Scheduled server maintenance complete
Our current server has been up non-stop for exactly a year. Over the last few weeks we had some slow loads and site errors, especially in blog comments. We did some scheduled maintenance a few hours ago, and the site was offline for a few minutes here and there.
The WordPress backend is up to full speed again. Comments seem to be faster, but we’re still not satisfied. We’re going to disable the Akismet spam filter and try some alternatives.
Today’s updates:
- System is updated from Debian 6.0.3 to latest stable release 6.0.6 and rebooted
- New version of eaccelerator is compiled for updated PHP 5.3.3-7+squeeze14
- Changed value ;suhosin.get.max_value_length = 1024 under /etc/php5/conf.d/suhosin.ini to solve errors related to piwik (traffic statistics software)
Please let us know how it’s working for you!
This entry was posted in site and tagged maintenance, server\.
Comments
comments are working :)
test1
test2
Test to see if comments are faster now….
Well…. Faster then before where I got a timeout 90% of the time, but it still takes a good 20 seconds to post a comment,
I have a feeling the remaining speed issue is related to the spam filter that contacts a 3rd party server. I’m going to try a few different services to see if there is a faster one, or we can just not allow links in comments by unknown users.
Comment with Akismet disabled :)
Slightly faster, but still 5-10 seconds. A forum post is almost instant with more info and database stuff to deal with. Hum.
Timed test
14s exacly
test3
Test without STC enabled…
reenabled
test4
GRC disabled
some hacks to comment.php
removed comment.php hack…
wordpress.org/support/topic/comments-are-very-slow-to-post
test
test5
test6
I was having slow load times in the forum – that’s speedy again now.
You can have a full timing report with the PHP extension Xdebug, although I wouldn’t enable it in production, you’d need to clone your setup somewhere to be totally safe for testing.
If the line says “;suhosin.get.max_value_length = 1024″ it’s commented out… changing it won’t do anything unless you uncomment it.
test7
@Ian, I sent an email about 5 minutes ago advising blog was fast (was very fast), but since then posted twice and noticed it was ‘ok’, but was taking maybe 15 seconds as a guess.
Yep, that last post took about 15 seconds also
Posting with a debug plugin enabled.
Posting with a debug plugin enabled…. just takes me to a white screen, so there must be some horrible issue between wordpress and the plugin,..
test comment
test with debugger enabled.
wp-content/plugins/get-recent-comments/get-recent-comments.php:1321 – get_settings is deprecated since version 2.1! Use get_option() instead.
But I have tried without it before. Disabled anyways and testing now.
Not it… Now timing all MYSQL queries
Total query time: 87.3ms for 52 queries (0.087296009063721s)
Total num_query time: 0.438 for 58 num_queries.
» Different values in num_query and query? – please set the constant define(‘SAVEQUERIES’, true);in your wp-config.php
Page generated in 422.9ms; (0.4228839874267578125000s); 79.36% PHP; 20.64% MySQL
Curious that the page generates in half a second, but still takes 10 seconds or more to display.
My best guess is there is a missing file or bad permissions somewhere and it tried to do something until a timeout or error limit is reached. I don’t see anything in the logs to point to it though.
Worst case is a problem up in the multiple layers of acceleration and caching.
Memory & Load Time
Load Time: 266.999 ms
Max Execution Time: 60
Memory Used: 48.57MB
Memery Total: 512M
Included Files
Total Files: 181
Total Size: 4.12MB
Largest: 180.08kB
Time to finish off the workshop video, enough PHP debugging for now.
For real this time :)
Test compared to alternate site
and another with updated group permissions.
test with firebug enabled