server overload

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 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?

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

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 could be worth trying too.

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;

Is this after upgrading to wp 2.1 ?

yes,after upgrading to 2.12 from 2.04