Resource Intensive!

Hi Jon,

Thanks for bringing this issue up. I will have a look into the issue. The admin-ajax.php file should only ever be hit on the admin side. If it’s being referenced on the front end, that would explain the large resource usage.

I will take a look and see what I can do about adjusting things.

Thanks,
Evan

Thanks!

Would you mind updating this thread when you get it solved?

I would like to use this in future projects.

Hi Jon,

I will certainly keep you posted when I get this issue squared away.

Thanks again,
Evan

Hi Jon,

I took a look into the issue and there were a few functions that were firing on the front end that shouldn’t have been, but they weren’t very resource intensive.

My guess is that you were running the p3 profiler on auto mode, and it was running through the backend admin pages of your site, which it does load a few more resources.

I ran p3 profiler a few times and noticed that it would spike high at the end of the scan, and by checking the ‘Detailed Timeline’ tab I could see that the last two spikes were coming from the dashboard.

Here are two screenshots of running an manual scan only browsing through the front end pages of the site.

https://cldup.com/ZsB6AqB1b8.png

Here is the detailed view of the plugin on the front end. You’ll notice that the plugin is the green line, and one of the less resource intensive plugins. I believe on whichever page you’re displaying you’re timeline on , the plugin loads masonry, a js file, a css file and font-awesome unless your theme is loading it.

https://cldup.com/W_uSYqoZ3I.png

Either way, I’ve shifted a few things around and pushed out a minor update which may speed up a few things on your end. You may want to double check what pages are causing the spikes, because I don’t believe it’s on the front end of your site and causing any page loading speed issues for your users.

Thanks,
Evan

Hello,

Thanks for the effort Evan.

I’ve done further testing and the intense loading time was not just your plugin. In fact it was probably very little due to Timeline Express

The offending plugin was Userpro. (should have guessed)