Kurt Payne

Hi James,

Just taking a quick look at the Currency Switcher plugin and it looks like the problem is the number of products you’re passing in. The plugin uses php’s include() to render the output for each price. This is a pretty normal practice (P3 does it, too) but it doesn’t scale to 1,000 prices well.

I can’t be 100% certain without running an xdebug profile, but php’s include() is known to be slow. It has to read the file (which means permission checks, file system access) and then parse it and convert it to object code and execute it. Using a recent version of PHP or an object cache (like XCache, APC, Zend Optimizer+, etc.) may help this.

Hope this helps! Good luck!

Hi Don,

Wincache wasn’t known to cause any issues when this was tested with php 5.3 with fastcgi and IIS 7. Not all conditions have been tested, though. If you’re using any other combination of versions, it may change things. If you’re using ioncube, zend guard, or any other zend extensions, that will also impact the results. It definitely sounds like there’s an opcode optimizer present that’s “fixing” the backtraces/ticks for php.

This graph shows that core is taking up more time than your plugin:

https://monosnap.com/file/wFCfWH13pXJnaNNssWq6aU3bYnTixJ

It looks like that last request is spiking and throwing off your average … that’s probably the plugins page? I can’t tell without the tooltip ??

That’s not that bad. You’re less than core time. 182ms average total plugin time is not that bad.

It should tell you the full path:

The scans are stored in /home/XXXXXX/html/wp-content/uploads/profiles and take up 50 KB of disk space. Each time you run a scan, this storage requirement goes up, and each time you delete a scan, it goes down.

Does this help you track down where P3 is trying to save your profiles? If the profiles folder is there and chmod 777, please ensure the uploads folder is writable as well.

Hello,

Are you wp-content for your content directory? Or are you using a custom content directory? Some plugins / themes will move your content directory, or you can define a custom location in your wp-config.php file.

Try looking in P3’s help page and look at this question: “How much room do these profiles take up on my server?” P3 will tell you where it’s trying to save the profiles.

What does the “Detailed breakdown” tab of P3 say if you eliminate all of the other plugins? It should just plot your plugin and each URL. That would narrow down the ‘slow’ URLs.

Hi Nocola,

Do you have any external API calls?

Hi nCrafts,

There is documentation with P3 under the “help” tab that explains in detail what is being measured.

Why would p3 show that the add-on pack is using 70% (again, 70% WHAT) ?

70% of wall time for php time only. CSS / JS are not considered unless they’re dynamically generated by the WordPress framework.

If wordpress takes 10 seconds to load, P3 has attributed 7 seconds to this plugin.

If you’d like more info, I’ve written all about it here:
https://kpayne.me/2013/12/24/write-your-own-code-profiler-in-php/

1. P3 provides no useful information on debugging the issue. All you see is 70% listed on different pages, presented in different styles. It’s the same piece of data. There is absolutely no other info, unless I missed some corner.

P3 is for profiling, not debugging. If you’d like to dig into this more, I suggest using any one of these other tools:

https://www.ads-software.com/plugins/query-monitor/
https://github.com/dannyvankooten/wp-plugin-profiler
https://github.com/Rarst/laps
https://wpperformanceprofiler.interconnectit.com/

Or jump straight into xdebug / xhprof and see where the holdup is.

2. FormCraft Add-On pack is a very small plugin. It loads no JS or CSS files on any page. It is a simple API snipper which connects forms to newsletter services. When your submit a form, this add-on connects to the, say, MailChimp server, giving them the email. Needless to say, this only happens when you submit the form. It obviously doesn’t happen every time you open a page?

I would look into this further for you, but the source code for the plugin in question is not available.

Hi all, I’m so sorry about that. There was a small bug in the 1.5.3.7 version and it’s been fixed in 1.5.3.8.

@mogulbuster Thank you. Updated in 1.5.3.8

Do you have any errors in your browser console?

@mogulbuster I think you’re on to something. I took a slightly different approach, but committed your fix in 1.5.3.7.

Have you tried with no other plugins and a default (twenty*) theme?

If you want to work together on this and don’t mind giving me access to your site, please email kpayne -at- godaddy -dot- com and we’ll see if we can figure it out.