@laserjobs we’re working on a better way to cache share counts. We’re currently using the Transients API – http://codex.wordpress.org/Transients_API to cache share counts for up to 5 minutes. For the quickest fix, we recommend turning off “server side share counts” from under Advanced Settings. This will stop your database from filling up and you’ll still get most of your share counters anyways.
Thread Starter
Zee
(@laserjobs)
This seemed to have happened during the last update. We have around 5000 posts with shares showing at the top and the bottom of the posts but I have over 36000 database entries. When I disable caching plugin like W3 Total Cache or Hyper Cache the site speeds right up again. So there is some sort of loop being created between the cache and shareaholic that it making massive amounts of database queries. I had to call my host becasue there were a bunch of 0 byte processes running that they had to stop manually.
I have disabled the “server side share counts” as suggested for now.
wp_options full of:
INSERT INTOwp_options` VALUES(1093546, ‘_transient_shr_api_res-963c80a5ab33edc3d5c1d079f519rdae’, ‘a:2:{s:6:”status”;i:200;s:4:”data”;a:1:{s:9:”pinterest”;i:20;}}’, ‘no’);
INSERT INTO wp_options VALUES(1093547, ‘_transient_timeout_shr_api_res-831h4da83f6e33a65b561c1bc8c789e8’, ‘1408114362’, ‘no’);
`
@laserjobs there were no changes made to the way we cache in the last update. Do you have a sense of which version you upgraded from? Have you always been on the latest?
@laserjobs do you mind emailing me your website URL so I can take a look? — jay@shareaholic.com
Thread Starter
Zee
(@laserjobs)
Now that I have turned off the “server side share counts” it seems to be working fine. Is there a way to clean up all those database entries that were injected into the wp_option table?
I have 2 sites with the same configuration this happened to.
Thread Starter
Zee
(@laserjobs)
At the time I was using Hyper Cache version 3.0.2 when my site went down
http://wordpress.org/plugins/hyper-cache/description/
When I switched to W3 Total Cache and it went down again but not sure if it was still writing entries to the wp_options table.
@laserjobs Glad to hear that things are working for you again! You could use WP-Optimize to clean up your transient entries: https://wordpress.org/plugins/wp-optimize/
Thread Starter
Zee
(@laserjobs)
So I got rid of all the following entries in mySQL a couple days ago:
_transient_shr_api_res
_transient_timeout_shr_api_res
Now I have 472 of each entry back again in my wp_options table. Why would they be getting created with the following entry checked?
“Disable server-side Share Counts API (unless there are issues with calling the service, it is recommended NOT to disable this API)”
It does not look like the entries are growing out of control this time but I am a bit concerned why they reappeared.
NOTE: I have cleared them out again and will see if they come back again.
Thread Starter
Zee
(@laserjobs)
Checked again and after 3 hours there has been 176 entries created since they were cleared out.
INSERT INTOwp_options VALUES(1325590, ‘_transient_shr_api_res-56613b9c5ac857e7186f3fbb524c74ed’, ‘a:2:{s:6:”status”;i:200;s:4:”data”;a:6:{s:9:”pinterest”;i:0;s:11:”google_plus”;i:0;s:7:”twitter”;i:0;s:8:”linkedin”;i:0;s:11:”stumbleupon”;i:0;s:6:”buffer”;i:0;}}’, ‘no’);
INSERT INTO wp_options VALUES(1325586, ‘_transient_shr_api_res-b06ba0ea2b66053d91006d7bafda6c87’, ‘a:2:{s:6:”status”;i:200;s:4:”data”;a:6:{s:9:”pinterest”;i:0;s:11:”google_plus”;i:0;s:7:”twitter”;i:0;s:8:”linkedin”;i:0;s:11:”stumbleupon”;i:0;s:6:”buffer”;i:0;}}’, ‘no’);
INSERT INTO wp_options VALUES(1325587, ‘_transient_timeout_shr_api_res-1406f7f47a6fcaed2d38b0b27d53edcf’, ‘1409272084’, ‘no’);
INSERT INTO wp_options VALUES(1325588, ‘_transient_shr_api_res-1406f7f47a6fcaed2d38b0b27d53edcf’, ‘a:2:{s:6:”status”;i:200;s:4:”data”;a:1:{s:9:”pinterest”;i:0;}}’, ‘no’);
The Shareaholic/W3 Total Cache combo was writing 100K rows to MySQL wp-options table per month until it finally crashed the site with a duplicate key error in MySQL.
I highly recommend disabling server-side Share Counts as the Author suggests
