Title: server overload Last modified: August 18, 2016 --- # server overload * [worpdress](https://wordpress.org/support/users/worpdress/) * (@worpdress) * [19 years, 3 months ago](https://wordpress.org/support/topic/server-overload-1/) * i have a dedicated server running my wp blog. i recently upgraded to wp 2.1 and 4 days after upgrading my server started to crash. my server admin told me my dedicated server was being overloaded by wp which is surprising because i only receive a few thousand visits each day. is there a known issue with wp 2.1 which overloads servers? * Thanks Viewing 6 replies - 1 through 6 (of 6 total) * [Pizdin Dim](https://wordpress.org/support/users/pizdin_dim/) * (@pizdin_dim) * [19 years, 3 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526646) * Overloaded how? What did they say? * While a few thousand visits is theoretically no trouble, it depends on how many concurrent ones you get. Sometimes, a badly configured database [query cache](http://lutrov.com/blog/144/) could drastically affect performance too. * I assume your host assures you that your server has sufficient physical memory and has the webserver configured optimally. * What do they claim? * Thread Starter [worpdress](https://wordpress.org/support/users/worpdress/) * (@worpdress) * [19 years, 3 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526647) * They tell me my dedicated server is being “overloaded” by my wp blog v2.1. the odd thing is i get no more visits than last year when there was no issue. * When you say “a badly configured database query cache could drastically affect performance too.” is that an issue with wp or something my server admin should be able to resolve? * Thanks * [Pizdin Dim](https://wordpress.org/support/users/pizdin_dim/) * (@pizdin_dim) * [19 years, 3 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526650) * If I were you, I’d ask exactly what “overloaded” means. In terms of the database cache, this is **not** a WP issue. Read the article I linked to above. My personal experience mirrors what that bloke is saying and as far as I’m concerned, it’s often something which is set incorrectly by database admins. * From what I hear from others, [WP-Cache](http://mnm.uib.es/gallir/wp-cache-2/) could be worth trying too. * [aigou](https://wordpress.org/support/users/aigou/) * (@aigou) * [19 years, 2 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526952) * hey,i was met the same issue. the sever is being overloading. the administrator have provided the slow-log to me as after. * > Most common slow queries: > 1. Time: 10% (775 sec) Amount: 9% (48 queries) > Avg. Query Exec/Lock Time: 16 / 4 sec. Used databases: [whutaig_wordpress] > Query example: use whutaig_wordpress; SELECT option_value FROM wp_options WHERE > option_name = ‘siteurl’; > 2. Time: 4% (360 sec) > Amount: 4% (25 queries) Avg. Query Exec/Lock Time: 14/ > 2 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > SELECT * FROM wp_posts WHERE ID = ‘329’ LIMIT 1; > 3. Time: 4% (326 sec) > Amount: 4% (22 queries) Avg. Query Exec/Lock Time: 14/ > 3 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN(137) > ORDER BY post_id, meta_key; > 4. Time: 2% (209 sec) > Amount: 2% (14 queries) Avg. Query Exec/Lock Time: 14/ > 3 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > SELECT comment_date_gmt FROM wp_comments WHERE comment_author_IP = ‘195.225.177.20’ > OR comment_author_email = ” ORDER BY comment_date DESC LIMIT 1; > 5. Time: 2% (164 sec) > Amount: 2% (14 queries) Avg. Query Exec/Lock Time: 11/ > 0 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > SELECT comment_ID FROM wp_comments WHERE comment_post_ID = ‘544’ AND ( comment_author > = ‘Business Loans’ ) AND comment_content = ‘Business Loans… nice blog!!…’ LIMIT > 1; > 6. Time: 2% (189 sec) > Amount: 2% (14 queries) Avg. Query Exec/Lock Time: 13/ > 2 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > SELECT ID, post_title, post_date FROM wp_posts WHERE ID = 142 AND post_status > = ‘publish’ LIMIT 1; > 7. Time: 2% (201 sec) > Amount: 2% (13 queries) Avg. Query Exec/Lock Time: 15/ > 3 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > DELETE FROM wp_comments WHERE DATE_SUB(‘2007-03-10 09:55:58’, INTERVAL 15 DAY) > > comment_date_gmt AND comment_approved = ‘spam’; > 8. Time: 2% (201 sec) > Amount: 2% (12 queries) Avg. Query Exec/Lock Time: 16/ > 4 sec. Used databases: [whutaig_wordpress] Query example: use whutaig_wordpress; > SELECT ID, post_title, post_date, post_content FROM wp_posts WHERE post_status > = ‘publish’ AND post_password =” ORDER BY RAND() LIMIT 5; * Thread Starter [worpdress](https://wordpress.org/support/users/worpdress/) * (@worpdress) * [19 years, 2 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526953) * Is this after upgrading to wp 2.1 ? * [aigou](https://wordpress.org/support/users/aigou/) * (@aigou) * [19 years, 2 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526954) * yes,after upgrading to 2.12 from 2.04 Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘server overload’ is closed to new replies. * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 6 replies * 3 participants * Last reply from: [aigou](https://wordpress.org/support/users/aigou/) * Last activity: [19 years, 2 months ago](https://wordpress.org/support/topic/server-overload-1/#post-526954) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics