Error during test – skipping failed benchmark…

P.S. I have a good server specification and also the benchmark score is: 8.8(it would be 9+)

AMD EPYC™ 9634 – 4 dedicated cores, 8 GB DDR5 RAM (ECC)

I thought i should mention this as i found a ticket on the support speaking about the same error but in that case you had replied saying – its due to the low server specification – which was true. But, for me this is not the case.

Here is another link to the screenshot of the benchmark:

https://ibb.co/xPZn75G

• This reply was modified 1 year ago by Unreal NFS.
• This reply was modified 1 year ago by Unreal NFS.

My bad!

I always ran the benchmark while the Query monitor plugin was still active as i wasn’t looking for the perfect score always; and if i wanted to get the perfect score i would deactivate it and run the benchmark. But, during both the benchmarking-methods benchmark never ever crashed for all these years after i started to use the WP Hosting Benchmark tool.

However, recently i upgraded the CyberPanel on both the servers – i ran the benchmark on an old WP install with 26 plugins with breakdance page builder(it has its own theme) – here we had no problem earlier when the benchmark was ran over 10s of times.

And on the other server, i installed a new WP with 5 plugins – this had default wp theme.

While running benchmarks in both the wp installations, i left the Query Monitor Active like always – that’s when the test crashed partially in the above.

I Deactivated the Query Monitor plugin and ran the benchmark – it worked without error!

I tested around 5 times to confirm this now using different combinations – Query Monitor was the reason behind the crash.

Sorry for the trouble as you had already explicitly warned that the Query Monitor could crash the test!

Thanks for the reply.

Great plugin BTW.

God bless.

Here is link to the new test:

https://ibb.co/XrpMtjFT

I am considering to deactivate QM on my live sites from today!

Since you have taken time to explain to me about Query Monitor, i thought i should speak about why i kept it ON even on a production site and what i does to minimize its impact on the performance.

I use QueryMonitor mainly to have more visibility into DB queries – just to see redis is working as it should, etc. For me, QM has become the defacto tool to find the performance stats in the toolbar.

I use a plugin by the name “Freesoul Deactivate Plugins” to deactivate QM in the frontend and let it run only in the backend.

I use another plugin by the name “Code Profiler” – this does the performance test of the whole WordPress installation and details how much time/resources each plugin is taking per visited URL!!! You can run the Code-Profiling of any page – it will give in-depth details.

Since the QM is disabled in the frontend – the code-profiling plugin shows that on my wp setup QM is not really costing anything at all in the frontend – its closer to zero impact.

Also, because db queries are mostly 95% hit @ Redis object caching – Admin-area is super fast already and code-profiling also shows QM’s impact is not much in the backend either though it does take some negligible performance impact that i can bare.

———————————————————————————-

However, after your above explanation – i think i must turn QueryMonitor OFF on the live site!

Thanks again, after all i won’t be needing QM after i know enough about my wp-setup.

=======> Also, a special thanks to you for your tutorial on improving WP’s performance – it helped my database performance a lot. Also, you are the reason why i don’t compromise on the CPU’s clockspeed anymore!

Thanks a lot – it was great listening from you – Anton Aleksandrov.

God bless. Thanks a lot.

I didn’t knew something that’s “crazy” about the WordPress until recently (especially after i got hold of Code Profiler) – that, pretty much all the plugins keep working even in the frontend while they are not used in the frontend and the case is same even when not all the plugins are used on a particular page in the frontend. I was aware about the CSS, JS files loading everywhere but wasn’t aware that plugin too loaded alongside!

“Usually, the number of the needed plugin on a specific page is lower than the number of globally active plugins.” —– This is crazy, as disabling certain plugins that’s not necessary on particular page or entirely on the frontend its a big deal.

"But regarding QM – isn’t it supposed to run and collect stats only when you are logged in as admin?"

QM still runs in the frontend – code profiler displays that it does along with the details in the Pro version!

I just tested on my newer wp install and deactivated QM in the frontend – and it stopped working 100% in the frontend. Earlier, QM was taking 0.001 of a second —– of course, it isn’t too much – but each bit matters especially when a site could get 1000s or even more visits and things can add-up pretty soon.

And yes, maybe QM or any such “Admin” exclusive plugin might not run every functions when it is running in the frontend, but it still loads and consumes some performance.

Thanks for more clarity about QM.

=====> I can share the copy of Code Profiler Pro with you. Just share me your public email ID – the plugin is not even a MB.

Great talking to you.

Thanks again.