PluginProbe
Code Profiler – WordPress Performance Profiling and Debugging Made Easy / 1.7.4
Code Profiler – WordPress Performance Profiling and Debugging Made Easy v1.7.4
1.9.5 1.9.4 1.9.3 trunk 1.4 1.4.1 1.4.2 1.4.3 1.4.4 1.5 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.6 1.6.1 1.6.10 1.6.2 1.6.3 1.6.4 1.6.5 1.6.6 1.6.7 1.6.8 All 40 releases
← All changes | lib/menu_faq.php +19 -0 trunk1.7.4 View file →
@@ -82,8 +82,27 @@
82 82 <?php esc_html_e('That can happen if your PHP version is 7.1 or 7.2. With those versions, Code Profiler can only use microseconds for its metrics, while with versions 7.3 and above it can use the system\'s high resolution time in nanoseconds. It can also happen if a PHP script has only a couple of lines of code, its execution time is too quick to be measured, hence it will show 0.', 'code-profiler') ?>
83 83 </td>
84 84 </tr>
85 85 <tr>
86 + <td style="border-bottom:1px solid #c3c4c7"><a name="composerwarning"></a>
87 + <h4><?php esc_html_e('Why does Code Profiler warn me that I have multiple plugins using Composer?', 'code-profiler') ?></h4>
88 + <?php
89 + echo esc_html_e('Composer, a tool for dependency management in PHP, is included in many popular plugins and themes. It is used to autoload PHP classes.', 'code-profiler') .
90 + '<br />' .
91 + esc_html__('Code Profiler will inform you if two or more activated plugins use it because you will need to take it into consideration when reading and interpreting the results. Let\'s take an example:', 'code-profiler').
92 + '<br />' .
93 + esc_html__('Assuming you have four plugins, #1, #2, #3 and #4. Both plugins #1 and #4 include and require Composer. WordPress will start and load plugin #1, which will run an instance of Composer to load its classes. Immediately after, WordPress will load plugins #2 and #3. Then, it will load plugin #4, which too will need to load its classes. However, plugin #4 will not start a new instance of Composer but, instead, will rely on the one from plugin #1 to load its own classes.', 'code-profiler').
94 + '<br />' .
95 + esc_html__('As a result, the execution time of plugin #1 will increase (its instance of Composer is used to load classes for plugin #4 too), while the execution time of plugin #4 will decrease (it doesn\'t need to start a new instance of Composer).', 'code-profiler').
96 + ' '.
97 + esc_html__('Therefore, if you have a dozen or more plugins using Composer, it is important to take into consideration that the execution time of plugin #1 may be much higher than other plugins.', 'code-profiler').
98 + '<br />' .
99 + esc_html__('Also, assuming you are a developer and just want to profile a plugin that you wrote and that includes Composer, you will need to disable any other plugin using Composer in order to get the most accurate results for your plugin only.', 'code-profiler');
100 + ?>
101 + <br />&nbsp;
102 + </td>
103 + </tr>
104 + <tr>
86 105 <td style="border-bottom:1px solid #c3c4c7">
87 106 <h4><?php esc_html_e('Is Code Profiler multisite compatible?', 'code-profiler') ?></h4>
88 107 <?php esc_html_e('Code Profiler is multisite compatible. Note however that for security reasons, only the superadmin can run it.', 'code-profiler') ?>
89 108 </td>