server overloading with 2.1

You can revert back to 2.0.x if you have a db backup of your site from that series.
If not, you’re stuck with 2.1.x as it alters some tables in the db.
Did you upgrade to 2.1.1 and it still does it?

thanks for the confirmation samboll. looks like i’m stuck with v2.1. yes it still does it with the wp v2.1.1 upgrade.

Can you elaborate a bit on the observed issue?

my website keeps crashing and the admin of my dedicated server simply says the blog is overloading the server. i should add, i’ve received no increase in traffic since upgrading to wp v2.1.

Tell your dedicated server admin that he is simply going to have to provide you with more details. How does he know the blog is the problem? What do the server logs say etc. You’re paying for them to support you, not play dumb ?? They need to help you troubleshoot the problem.

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;

this could be a wp 2.1 issue/bug. try installing wp-cache, it helps a little.

thank you.
the issue is be caused when i updated to wp2.12.
now i must to promise that the overload is not happen more,so i am waitting the root-solve,maybe wp-cache is be working,i hope.