I got a warning from my host that I am using to many resources... CPU_TIME:241 table_rows_read:361785690 SELECTS:12571 ROWS_UPDATED:752 ROWS_FETCHED:308815 BUSY_TIME:248 ONNECTED_TIME:561 BYTES_SENT:55647984 BYTES_RECEIVED:4075955 WAIT_TIME:7 Then they list about 20 sites, most get no traffic.... DB_USER: xxx_store -- TOTAL_CONNECTIONS: 9 -- CONNECTED_TIME: 234 -- CPU_TIME: 197 -- TABLE_ROW_READS: 349934385 -- SELECT_COMMANDS: 3130 -- UPDATE_COMMANDS: -- BUSY_TIME: 201 -- BYTES_SENT: 46656385 -- BYTES_RECEIVED: 197279 -- WAIT_TIME (IO): 4 Then they list this.... Infinite WP - Blog Management Script 30647 0.0 0.0 317620 19760 ? SN 22:22 0:00 /opt/php53/bin/php-cgi /home1/xxx/public_html/xxxxxx.com/blog/execute.php Something else they list: WP Blog 30670 9.6 0.1 351380 54196 ? SN 22:22 0:22 /opt/php53/bin/php-cgi /home1/xxx/public_html/xxxxx.com/wp-admin/index.php I did install Infinite which is a blog management script a few days ago, so I dont know if that is the cause or what is going on..... What do you guys think?
The issue is because the Blog Management script is used to access multiple wordpress databases & thus it access all the databases at regular intervals or whenever a task is performed. Please check the below steps to fix this issue. 1. Make sure the blog management script does not read too many unnecessary rows in db queries or modify the script to just read the necessary database when a task is performed. 2. Need to upgrade hosting packages. Move off of a shared hosting platform and look to host your website on a dedicated or virtual server. So the best option will be to uninstall this script , if not enhance the server capacity (server plan upgradation). Hope this helps
Found the issue; a log file was building to more then 500k causing the server to use more resources.... removing the log file from the domain in question did stabilize resources, but not by much... resources are so slim now that I can not even run the basic of tasks ie: sitemap..... If I attempt to run any internal tasks, or there is a hiccup with any of the domains, then resources will quickly spike until the task is over. Like you said, next step would be to upgrade....