New answers tagged performance
As already stated, the method you are using is the recommended way of doing it. Wordpress is written in such a way that it will always look for a template in a child theme first if there is an active child theme before looking for a template in the parent theme. So coming to performance, there is no impact on performance as these checks are performed ...
Actually, what you have described is the correct way to do things and there shouldn't be any noticeable impact on site speed and performance. Using child themes also has the benefit of allowing your changes to persist through theme upgrades.
I'm not sure if this will help you with your ajax call, but Plugin Organizer is a well-supported plugin that enables the selective loading of other plugins based on URL. It works great on my site.
Query results for posts, terms, and metadata get placed in cache. If a function is called that accesses data from previously queried objects within the same request (or you're using a persistent cache mechanism that maintains data across requests), it will not trigger another query and will instead fetch the data from cache.
It seems like yes it depends whether it does create a new query or not. As Milo has pointed out in his answer, WordPress using a caching system. The function stack looks like this: get_the_permlink() calls get_permalink() calls get_post() which when given a post ID does this: $_post = WP_Post::get_instance( $post ); which looks like: /** * Retrieve ...
Haven't actually seen plugins with 30 shortcodes, but my opinion on this is, it is too much and I would really want to know what are all these shortcodes for. To come back to the actual issue, shortcodes is slower than normal functions because they need to be parsed. This differences should be minute though. The real performance issues comes in when it come ...
It sounds like you misunderstand how to add rewrite rules as your structure is relatively common and should not require flushing the rules on every page load. The impact depends on your set of rewrite rules, and the codex is somewhat outdated and I don't think it is as bad as it used to be several versions ago, but still it is updating an option with a ...
Another answer to this is to look at performance increases in PHP 5.5, PHP-NG, and HHVM over PHP 5.3 and PHP 5.4. No necessarily a direct memory efficiency gain, but using PHP < 5.5 without (especially without an opcache) is leaving a lot on the table. Some links to benchmark results: ...
Top 50 recent answers are included