[wp-hackers] APC-Nginx-Apache problems / memory problems on VPS
ronin at braydon.com
Mon Aug 29 11:54:56 UTC 2011
The biggest problem I've found is the interoperability between other
plugins and caching plugins, since caching isn't part of the core. This
is especially true for any plugins that deal with templates or post
types or plugins that use their own database tables. That is to say
caching isn't a part of the core other than the transient API, right?
But that works with the database still if not using the memcache plugin,
and the database is usually always the biggest bottleneck, when static
file would be better when memcache isn't available.
On 08/29/2011 04:42 AM, Martin Lazarov wrote:
> And that's the way many of the cache plugins works. But that
> complicates the situation and only one mistake make the plugin to work
> worst than clean wordpress installations without any cache plugin
> On Mon, Aug 29, 2011 at 1:28 PM, Braydon<ronin at braydon.com> wrote:
>> The most ideal situation:
>> Caching repeated independent elements as static html, widgets, post
>> summaries, post details, post comments, all as separate, and each with their
>> own URIs that can easily be invalidated. These can either be cached in
>> memory or on disk and accessed via PHP or from Nginx or Apache. This way
>> across the wire for every page, and the server doesn't need to do any work
>> generated that would lead to all posts, comments, pages....
>> On 08/29/2011 02:53 AM, Daniel Fenn wrote:
>>> That because not all caching plugins are created are not the same. Some
>>> better written than others and some only deal with some aras.
>>> On Mon, Aug 29, 2011 at 7:47 PM, Braydon<ronin at braydon.com> wrote:
>>>> caching plugins?
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>> Colors of Digital Freedom
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
Colors of Digital Freedom
More information about the wp-hackers