Updating from Version 2.5.5 to Version 3.0.8 caused high processing

In your case switching back the caching method to “refresh cache” will have the same result like switching back to mashshare 2.5.5.

You find that setting on the general tab.

I have to investigate more why the async caching method increases your load. Usually there is only a very small increase in load once every 1 hour for new posts and once every 4 to 12 hours for older posts.

Are you using any caching plugin like w3 total?

Filling the cache for all posts with the new caching methods needs some time.
After a first initial loading phase with higher load the load should be lowered to a minimum after a while. (lessthan before because the async cache needs less resources after cache is filled )

How long have you waited before you switched back to MashShare 2.5?

Think i have found the issue. Will be fixed in next version

Yea, we are using W3 Total Caching. Our refresh cycle is 1000 posts every hour.

I believe we had the plugin updated for 3 hours before our logged in users began experiencing 502 Gateway errors due to the CPU overload.

Also due to the high traffic of our live website once the 502 errors began we have to revert right away, but looking at the logs, the Resource temporarily unavailable error was occurring off and on for three hours before it caused the 502 errors to be visible.

Thank you. Once a new version is available we will cautiously test it. Possibly with the “refresh cache” option on this time.

It would be excellent if you could give version 3.0.9 a try. You find it on github: https://github.com/mashshare/Mashshare

Please read here about how the async mode works, so you understand how to test that feature: https://www.mashshare.net/documentation/shares-are-not-updating-or-are-not-accurate/

Tl;dr:
After installation of the update purge your site cache and fill it again manually or by using any preload function. Than go to any posts and check the source code for something like:

var mashsb = {"shares":"305", ... REMOVED ... "refresh":"0"};

You see there a variable named refresh which must be 0 on initial load. This variable is for triggering the async cache refresh.

If its 1 and keeps 1 even after a page reload switch back to caching method “refresh while loading” and i investigate more into this.