No, notices by themselves are not a performance issue and generating them typically doesn’t take considerable resources (there are exceptions if you are replacing error handler – I seen it get slow because of larger output volume and conflicts with antivirus). Of course what they do indicate is potential issues with code quality, which is … Read more
Turn off all plugins. Switch to TwentyTen. Then install the debug bar and helpers. Then switch back to custom theme – reload. Turn one plugin on – reload, next plugin – reload, etc.
Try one (or more) of the below methods to increase the memory allicated by PHP. First try increasing the limit to 64MB, and if that fails use 96M. You can define the WP_MEMORY_LIMIT constant in wp-config.php: Increase PHP Memory to 64MB define(‘WP_MEMORY_LIMIT’, ’64M’); Increase PHP Memory to 96MB define(‘WP_MEMORY_LIMIT’, ’96M’); You can also change the … Read more
you can try some of these extra parameters: ‘update_post_term_cache’ => false, ‘update_post_meta_cache’ => false, ‘cache_results’=>false, ‘no_found_rows’ => true, ‘posts_per_page’=>1, ‘post_status’=’publish’, ps: you can measure the speed of your query when you are testing it with microtime() http://php.net/manual/en/function.microtime.php Edit: Here is a another way: function count_votes($user_id=1, $question_id=1, $post_type=”vote”, $meta_key=’comp_question’){ global $wpdb; $sql = “SELECT count(*) FROM … Read more
Sagive, wp-blog-header.php loaded in the index.php on each page request. AJAX calls included (if that’s what you mean “time after time”. Then it loads template-loader.php. This has nothing to do with the SQLs you see, and not with the “spikes”. Install the Query Monitor plugin to see your SQLs better in the Debug Bar. Do … Read more
Edit line 149 in file.php as described in this thread: https://wordpress.org/support/topic/unable-to-update-plugins-after-upgrade-to-42 fixed it for me (on a linux host). edit: just read you are on windows: someone also posted a fix that applies to windows hosts there (apparently more complicated because backslashes are used in filepaths). so your line 149 in file.php should read: if … Read more
If you are on any environment you did not personally set up, you may not have the permissions to override the php.ini file. Also some plugins can manually do: ini_set( ‘memory_limit’, ‘512M’);
The true maximum is ultimately up to the host – they can impose whatever limits they wish. But even so, you can try with WP_MEMORY_LIMIT, which is the memory limit WordPress sets at runtime for any given request. WP_MAX_MEMORY_LIMIT is only applied in certain situations, either for administrators in the backend (users with the capability … Read more
Because of this line in wp-admin/admin.php: if ( current_user_can( ‘manage_options’ ) ) { wp_raise_memory_limit( ‘admin’ ); } In other words, WordPress raises the memory limit to WP_MAX_MEMORY_LIMIT within the admin, but only for users with the manage_options capability i.e. administrators. Your best bet is to raise the default memory limit in your wp-config.php: define( ‘WP_MEMORY_LIMIT’, … Read more
No and even if you could, if the plugin ran out of available memory then the entire page generation would stop due to the fatal error. You’re better off fixing the plugin itself to not use as much memory or to just further increase the total memory allocated to WordPress/PHP.