WP RAM hog

Grindstone said:
^^ What plugin do you recommend for that? I've tried a few I found but no improvement in performance.
Click to expand...

Don't use a plug-in, simply add the following line to your wp-config.php file:

Code: 
define('WP_POST_REVISIONS', false );

Add the above just before this line of code:

Code: 
require_once(ABSPATH . 'wp-settings.php');

To delete any post revisions already saved log into phpmyadmin or some other mysql admin and run the following command:

Code: 
DELETE FROM wp_posts WHERE post_type = "revision";

There you go, post revisions are disabled and deleted in just two simple steps. Downloading and running yet another plug-in is not required.

Enjoy!
 


^^ Thanks, good stuff. googled upon the delete from wp_posts and ran that a few hours ago, seemed to speed up the back end somewhat. Will play with the wp-config code now.
 
If you are using auto tag generators and XML sitemap generators, disabling the 'tag pages' option in the sitemap generator might make a difference. I used to have to do that a lot with blogs that had 10,000+ posts
 
Grindstone said:
^^ Thanks, good stuff. googled upon the delete from wp_posts and ran that a few hours ago, seemed to speed up the back end somewhat. Will play with the wp-config code now.
Click to expand...

I use a plug-in called "Cleanup Wordpress" that does all that and more with a click of a button. Just DL it.
 
OK, have done all of the above, with the exception of the Slashdot article refrozen linked to. Looking at it in Putty, the php query when I hit edit pages causes the CPU to spike to 100%. Anybody run into something similar? Googled and searched WF to no avail. Thanks!
 
My rules:

WP + W3 Total Cache + APC = Win
Nginx + FastCGI + Above = MegaWin
MySQL + slow query log + manually creating relevant indexes (honestly can't remember off the top of my head the precise one, changes sometimes from version to version) = MegaSuperWin
 
moomycow said:
My rules:

WP + W3 Total Cache + APC = Win
Nginx + FastCGI + Above = MegaWin
MySQL + slow query log + manually creating relevant indexes (honestly can't remember off the top of my head the precise one, changes sometimes from version to version) = MegaSuperWin
Click to expand...

Hrm I already do the MegaWin line except I'm not using "W3 Total Cache" but rather wp-super-cache. What rewrite rules are you using with W3 Total Cache? This is what I'm using with wp-super-cache so that php is completely bypassed (like its supposed to) when static/gzipped cached content exists:

location / {
# Enables the Gzip Static Module (this must be added via --with-http_gzip_static_module
# Compile option when you compile Nginx in order to use Gzip Precompression
# If you don't have it installed you'll only be able to serve the uncompressed html files
gzip_static on;

# Disables serving of Gzipped content to IE6 and earlier
gzip_disable "MSIE [1-6]\.";

# Sets the default mime type to text/html
default_type text/html;

if (-f $request_filename) {
break;
}

# Prepares some variables to aid us in determining the existance of the cache
set $supercache_file '';
set $supercache_uri $request_uri;

# Do not use the cache when submitting something such as a comment (ie: goto PHP)
if ($request_method = POST) {
set $supercache_uri '';
}

# Do not use the cache when submitting a query (ie: goto PHP for parsing)
if ($query_string) {
set $supercache_uri '';
}

# Do not use the cache where it may cause problems
if ($http_cookie ~* "comment_author_|wordpress|wp-postpass_" ) {
set $supercache_uri '';
}

# If the variable has not been emptied assign the usual cached file location
if ($supercache_uri ~ ^(.+)$) {
set $supercache_file /wp-content/cache/supercache/$http_host/$1index.html;
}

# If the cached file exists, rewrite the browsers request to the cached file location
if (-f $document_root$supercache_file) {
rewrite ^(.*)$ $supercache_file break;
}

# If the cached file location does not exit, or is blank, and the file requested does not exist
# Fall back to index.php to be parsed dynamically
if (!-e $request_filename) {
rewrite . /index.php last;
}
}
Click to expand...
 
I did some research, just figured I'd toss it in this thread... if you're bypassing PHP entirely, Super Cache is as good as Total Cache (for obvious reasons). If you're not (and just using its built in WP_CACHE implementation), total cache is faster in my very limited testing.
 
You must log in or register to reply here.
Top Bottom