2 Apr 02, 2008 00:11
1. You should absolutely optimize it from time to time, but I don't know how much server power that'll save you. Take a look at your tables and see how big they are. Especially hitlog and sessions. You can empty those ( and basedomains and useragents ) without adverse affect other than requiring a fresh login and reduce some server load by the way.
2. Technically this will help but you have to ask yourself how much server power it takes to generate a post versus the rest of the page. I'm only guessing, but I think the posts are small compared to what you may have going on in the rest of the page. Sidebars and such.
3. There are settings you can control this stuff with. I don't know where off-hand, but a number of days to keep the hitlog active for. Set it to "1" and you'll keep some tables from growing to huge proportions. Also there are checkboxes for logging all hits on all public pages and all hits on admin pages. Uncheck them both and obviously hit logging pretty much goes away. Still set the other setting to "1" days worth because I think that affects your sessions. MAYBE NOT. In fact, probably not, but it can't hurt to try...
I believe the "who's online" widget gives credit for being online up to 5 minutes after someone leaves ... but doesn't count them again if they come back. So ditch the "who's online" widget and see if your cpu usage goes down. That'll tell you if it is a measurable component of your overall server load yah?
This assumes you have the ability to see and track server load of course!
5. How often do you post, and how many bloggers do you have? Frequently changing "first post" blogs won't benefit much from it, but if you post only occasionally - and especially if you are your only blogger - then you might consider generating a static page each time you post. What that does is nail a snapshot of your blog's entry page and provide an html equivalent. Thus the php execution to make the page is removed for anyone visiting only the main multi-post page. I've never done it so I don't know jack about how it actually works though.
5. Lose some sidebar stuff. I've no idea how much you use, but ask yourself if it is REALLY what you want on your sidebar. If not ditch it. EVERYTHING in the sidebar takes server power to generate, so lose what you thought "hooray" about but now might think "not worth the power it takes".
5. Build your skin to have either no sidebar on single post pages, or, to have a radically scaled down sidebar on single post pages. Evopress has no sidebar, so there is an example of doing that. Alternatively you could make a single post page include "Sidebar Single" container, then add only a couple of widgets to that container. This would be particularly helpful in situations where you use the "read more" feature because anyone reading more will currently get the full whammy again, but could be served a "low calorie" version. Commenters are obviously clicking through, so you'll save some cycles on page loads prior to commenting.
5. Write total crap. One of the best ways to save your server is to post stuff no one wants to read. Eventually even the search engines will get tired of crawling you because - if your posts suck enough - they'll just give up in disgust. This is the way I keep my traffic low. Works great!