kohashi

I’ve talked to the BuddyBoss folks before and I probably encouraged them to feel free to use the code which is used in WPPerformanceTester. The original of my plugin was mostly a wrapper of other open source benchmarking scripts. That’s how open source works. I’m happy to see the impact of the plugin expand whether under this name or being incorporated into others. If the Buddy Boss team finds the plugin valuable and brings that value to an even larger audience within the community, that’s amazing.

No problem, it’s probably helpful to post this all publicly for anyone else.

It is this line right here: https://github.com/kevinohashi/WPPerformanceTester/blob/426ffe4f91f8a39604ab8921e06cdf913b62a524/benchmark.php#L172

$query = “SELECT BENCHMARK(5000000, AES_ENCRYPT(CONCAT(‘WPHostingBenchmarks.com’,RAND()), UNHEX(SHA2(‘is part of Review Signal.com’,512))))”;

It’s running 5 million AES_ENCRYPT functions on your SQL server.

It is designed to take a while, and is 100% something that you would never do on a real production server. The goal is creating something heavy enough that we can measure the difference between systems. If everything handles something in 10ms, it’s harder to see a difference, and even harder as things go forward. I tried to create a function and run it enough times that it took a while. On purpose. That way it’s easier to see the difference between platforms and take into account things will likely get faster in the future.

I wouldn’t worry so much about the number itself (compare it against the benchmark of submitted scores) and compare it against different versions of your own setup. The actual raw number in isolation doesn’t mean a whole lot.

I hope that explains everything and helps you out. If not, please expand on your issue and I will try to answer.

I tried to respond to your query over email before, not sure if you received it.

So the plugin was updated and the new version uses different benchmarking algorithms. The old ones were having issues (some functions were removed/deprecated from PHP and mysql). So the numbers are explicitly NOT comparable between the old version and new.

The spirit is the same and 2.0 results will compare to 2.0 results in the graphs. 1.x results will compare against 1.x results (if you’re still running the old plugin). But 1.x and 2.0 results are apples-to-oranges different.

I am never thrilled to lose the history of benchmarks but when the functions used are no longer compatible with the latest versions of the software they are built on, it’s a breaking change that has to happen unfortunately.

This seems to be a 7.4 issue (the deprecated warning), older versions would have all worked the same.

I won’t be pushing out that change quite yet, there are a few bigger issues I want to solve. This would be a breaking change in terms of comparing performance between results. So I want to group all those together and do it at once rather than have versions that have changes that the results will be meaningless against all old ones and new ones shortly after.

Hope that makes sense.

Thank you for the report. I’ve updated the code on github merging in that pull request and going through all the old pull requests there. I’ve also applied the changes the plugin here on .org.

Appreciate you giving me the push and reminder to fix these things.

If you wouldn’t mind giving it another try to confirm it’s working again it would be appreciated.

Could you post the error messages? What version of WP / mysql / php are you running?

I wish it was less of a hassle to update the plugin compatability, but yes, it should still be working just fine for most setups. Glad to hear you had a good experience.

Just wanted to say thank you, the new version seems to have taken care of this issue.

So the host isn’t blocking them, I’ve been working with them trying to diagnose the issue (Pressable is the hosting company). Are the 429 and cache error are related based on what you’ve described? If the plugin is using the cache and trying to make a server side call instead for most requests. I’m logged in and it’s failing, so is it defaulting to browser request and that is getting the API blocked with 429s? They come and go, it’s not always erroring 429, but cache is definitely never working at the moment. Reconnecting the account does update what is in the cache though.

brightestyoungthings.com, it is only showing the error on admin side. I am also now getting 429 errors on admin side only.

I’m running into a similar issue except re-installing/reconnecting doesn’t remove the error anymore.

I think it’s solved now. The issue was another instagram plugin hitting the API as well ans using up all the calls.

Was there a resolution for this bug? I think I’m running into something similar.