eg33k are you hosting on hostgator?
can you share the adjustments you made to google sitemaps?
ALso if you can explain the process a little about hard coding the templates, would be great.
I just recently switched over to hostgator from another host because of server load issues.
I am on a baby plan and it says its "unlimited" , but the inodes thing is a little concerning. I did read somewhere that someone fought them on this and won.
did you disable your cron.php and use crontabs?
Thanks
Nope, not on hostgator, sorry. Liquidweb.
For google sitemap plugin:
Building mode:
Rebuild sitemap if you change the content of your blog (unless you are making several updates per hour autoblog updates, but it depends on the quantity of changes) Imagine addin 100 new posts per day on a site with 3,000 posts, and rebuilding your sitemap many times per day; this could eat up some resources. If your AB is really huge you may want to manually rebuild your sitemap once every week or two.
I write the normal xml file, but not the gzipped file
I Add sitemap URL to the virtual robots.txt file (ONLY if i don't have a real robots.txt file to start with!)
Tweak Advanced settings (increase memory limit/execution time/build in background)
In sitemap content settings I choose only:
Include homepage
Include posts
Include static pages
Include the last modification time.
(enabling other, seems to slow down the sitemap generation process as it results n a much bigger file size)
Change frequencies
I don't set too many 'Daily' change frequencies,
Editing dynamic "links" and hardcoding them:
If you look in Appearance-Editor-header template, you will see there are dynamic database calls used to pull in images, text, links, etc. Sometimes reducing the number of database calls is as easy as hardcoding the paths fro image, links, etc. - IF the usage problem is due to excessive database calls, this might help. This trick can work in the footer as well.
I don't have much experience with page caching or widget caching plugins, but other have found them to be useful.
To be honest, I never tried directly editing my cron.php, but setting the timing of your crons to avoid crons running too frequently or when backups or other processes are running (using WP-Crontrol) can help.
I get the feeling that WP is a bit like Micosuckt, each new update version requires more overhead (I could be wrong) and that some plugins simply do not play nice with certain WP versions.
I once found that simply changing my Theme made a HUGE difference in one of my ABs. So even Themes are not always optimized for minimal server resource overhead!
Hope this helps a little more. Good luck!
-sorry for rambling and typos...