Server CPU Usage

[Stacey]

Stacey

October 27, 2017 at 11:15 am

We’ve used Virtue for years, but in the last two weeks our host (siteground) has shut down our site for spikes in CPU Usage. Here is the most recent information from them. Does this make any sense to you…I got nothing.

Stacey
_____________________________________________________

Avatar
Georgi Ganchev
Support GuruPosts: 25290Posted On 27 Oct, 2017 11:59 CDT
Hello Stacey,

Since you have reached limit which is 4 times higher than the one allowed for your hosting plan there is no more options to increase it on our end.

I have increased it a little bit now and the site is online.

We have conducted a detailed investigation and it turned out that your application executes slow queries towards its database, which eventually hogs the server. The server tries to execute your slow queries while putting other processes in the queue until some memory is freed. While they are waiting however, they stack up and cause further problems. There can be many reasons for slow database queries, but the following 3 are the most common ones:

1. Large database
2. Not well written scripts
3. Large number of internal links that query the database directly.

Code:
=== Databases Info ===========================================================
Database Tables Views InnoDB MyISAM Slow Queries Slowest Query DB Size
————– —— —– —— —— ———— ————- ——-
mealslik_db 80 0 35 45 9 3.024 78.8 MB

Code:
=== TOP 9 of 9 (total) Slow Queries for the past 24 hours ==========
1. Executed 17h 19s ago for 3.02381 sec on Database –> mealslik_db
Date: 2017-10-26 18:57:39 Query_time: 3.023810 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000096
# Schema: mealslik_db Last_errno: 0 Killed: 0 UPDATE wp_wsek_options SET option_value = ‘0’ WHERE option_name = ‘rhc_recurr_version’;
————————————————————————————————
2. Executed 1h 50m 17s ago for 1.635692 sec on Database –> mealslik_db
Date: 2017-10-27 10:07:41 Query_time: 1.635692 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000102
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘11269’;
————————————————————————————————
3. Executed 55m 23s ago for 1.594213 sec on Database –> mealslik_db
Date: 2017-10-27 11:02:35 Query_time: 1.594213 Rows_examined: 0: Rows_sent 0 Lock_time: 0.000121
# Schema: mealslik_db Last_errno: 0 Killed: 0 INSERT INTO wp_wsek_options (option_name, option_value, autoload) VALUES (‘_site_transient_timeout_http_worker_lock’, ‘1509120213’, ‘no’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload);
————————————————————————————————
4. Executed 2h 9m 12s ago for 1.551562 sec on Database –> mealslik_db
Date: 2017-10-27 09:48:46 Query_time: 1.551562 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000089
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘10765’;
————————————————————————————————
5. Executed 18h 23m 45s ago for 1.546859 sec on Database –> mealslik_db
Date: 2017-10-26 17:34:13 Query_time: 1.546859 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000088
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘8697’;
————————————————————————————————
6. Executed 1h 44m 13s ago for 1.442539 sec on Database –> mealslik_db
Date: 2017-10-27 10:13:45 Query_time: 1.442539 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000081
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘11426’;
————————————————————————————————
7. Executed 18h 38m 13s ago for 1.24591 sec on Database –> mealslik_db
Date: 2017-10-26 17:19:45 Query_time: 1.245910 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000055
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘8328’;
————————————————————————————————
8. Executed 17h 3m 27s ago for 1.208931 sec on Database –> mealslik_db
Date: 2017-10-26 18:54:31 Query_time: 1.208931 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000058
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘9795’;
————————————————————————————————
9. Executed 1h 5m 59s ago for 1.080231 sec on Database –> mealslik_db
Date: 2017-10-27 10:51:59 Query_time: 1.080231 Rows_examined: 1: Rows_sent 0 Lock_time: 0.000091
# Schema: mealslik_db Last_errno: 0 Killed: 0 DELETE FROM wp_wsek_queue WHERE id = ‘12406’;

You could check the following articles for more information on how to optimize your database:

*Login to see link
*Login to see link

*Login to see link

*Login to see link

Furthermore, you may consider contacting a third party developer who will be able to help you resolve the issue.

Best Regards,
Georgi Ganchev
Senior Technical Support