Or just static generate it with whatever plugin, save the file it generates, and upload it. Then disable that plugin. Repeat as necessary.
WP RAM hog
- Thread starter turbolapp
- Start date
Or just static generate it with whatever plugin, save the file it generates, and upload it. Then disable that plugin. Repeat as necessary.
I'd recommend this - Google (XML) Sitemaps Generator for WordPress
You can limit the number of post in the sitemap by editing out the options.
Also for the link that you need to visit to update the cron - there's no need to manually visit it. Use FREE Cron Jobs - Reliable Web Cron service - Set Cron Job PHP - It's a great web based Cron Service!
You can limit the number of post in the sitemap by editing out the options.
Also for the link that you need to visit to update the cron - there's no need to manually visit it. Use FREE Cron Jobs - Reliable Web Cron service - Set Cron Job PHP - It's a great web based Cron Service!
Have you had any luck with any of this? I've been dealing with the same issue for the last few weeks. I've tried a ton of different solutions with little or no results at all. Seems like most of my issues started with 2.9.
Not really 
I mean trying almost all the solutions brought it down about 10% which is nice but nothing to cheer about. The theme seemed to use the most when I switched it to default it dropped another 20%. But then you kinda get into the whole, well what the fuck is the point of using wp if you can't use any of the stuff that makes wp so great? annoying as hell.
I mean trying almost all the solutions brought it down about 10% which is nice but nothing to cheer about. The theme seemed to use the most when I switched it to default it dropped another 20%. But then you kinda get into the whole, well what the fuck is the point of using wp if you can't use any of the stuff that makes wp so great? annoying as hell.
Great tip, thanks. I have a couple of high traffic sites that are killing the page load time. I am going to test this out.
I have a WooThemes WP install (FreshNews) and I notice that fucker is bloated as hell. Between 3 .css files, javascript, and all the images, the number of http requests was around 18 if I remember correctly. I condensed all the css files, got rid of the extra javascript and unnecessary images... and I'm down to 1 http request. Web Page Analyzer - free website optimization tool website speed test check website performance report from web site optimization
not sure how much that helps with regard to RAm usage because Im a retard when it comes to this stuff... but I think WooThemes is simply way too bloated by default.
not sure how much that helps with regard to RAm usage because Im a retard when it comes to this stuff... but I think WooThemes is simply way too bloated by default.
Not really
Use both W3 Total Cache and PHP level caching. Combine this with a well configured .htaccess file to do browser side resource caching and perhaps a CDN (Amazon S3?) and all that memory use won't matter anymore.
Seriously. It'll be fast - keep in mind that when you're caching, the memory use only matters when the page is being regenerated; which shouldn't be for most users.
Thanks for the tips, I've got W# installed and configured and it made some difference but not much. I need to check out my .htaccess and look in CDN as well and see if that helps out.
Biggest wordpress site I worked on suffered some serious bloating issues too. I tried optimizing the databases, but ended up just recommending a server with more RAM.
Supercache addresses the problem in that if you set it up right (eg .htaccess rules), the request never hits the PHP interpreter. It's served as an HTML file right off disk.
Sitemap plugins shouldn't be hooking into any part of the regular request cycle. They only get run when you make a post. That "external trigger" someone talked about is only if you're dumping in posts outside the wordpress admin or API.
PHP by nature is a RAM pig. There's nothing wrong with that. The problem happens when you couple it with the pre-forking model of Apache. So you've got 30 some httpd processes, each with 30-50MB of PHP weight. Practically, only 3-5 of those could be working at any given time before you get contention.
One thing to do is lower the maxrequestsperchild parameter in Apache. This will kill off children after fewer requests, who will be replaced by fresher ones.
Since moving to nginx and using PHP workers through FCGI I've never looked back, though. You keep a few php processes going and requests are only sent to them if needed. Much better for a VPS.
Sean
Well, if you have a bloated wordpress site and it's a money site and you really need to figure things out, a good test is to take a default wordpress installation, no special themes or plugins or anything, and edit the wp-config file to hook it up to the database of the bloated install. Then see if load times on the clean install are as bad as on the original.
That won't fix anything, but it will tell you if you have database issues or theme/plug-in/otherphp issues...
That won't fix anything, but it will tell you if you have database issues or theme/plug-in/otherphp issues...
I've had problems with a WP language translation plugin Wordpress Global Translator Plugin | Nothing2Hide
It's a great plugin but I found this was making my site slow after a while, a cache folder had 1000s of files in it and site backups were like 350MB! I deleted the plugin and site backups are only about 20mb now. Might be a possible solution.
It's a great plugin but I found this was making my site slow after a while, a cache folder had 1000s of files in it and site backups were like 350MB! I deleted the plugin and site backups are only about 20mb now. Might be a possible solution.
This is terrible advice in the context of this thread. We already know its plugin/theme issues, but themes/plugins are what make WordPress awesome. We're discussing ways to deal with it without sacrificing the powerhouse WordPress is - and HTML-level caching with W3, combined with client side caching headers and all that great stuff are really what it comes down to.
Joe.
Also, holy shit, delete your revisions. 800 revisions throws the memory use over 40MB just to load a post.
800 revisions doesn't take long to hit on an active site...
800 revisions doesn't take long to hit on an active site...
^^ What plugin do you recommend for that? I've tried a few I found but no improvement in performance.
Thanks G, thats one of the ones that I installed and ran last night. So cross that off the potential issues.
