Hot answers tagged

3

There is no query based way to get server state. Glue, negative cache timers, etc. must be dumped from memory using the rndc dumpdb command. Record types beginning with \- are negatively cached. \-A, \-AAAA, etc. \-ANY indicates a true NXDOMAIN. No records live alongside or beneath this entity. The above might be confusing if you have not been exposed to ...


3

In general caching works poorly with dynamic content, especially with content that contains things like "recently viewed" that will change every singe page load. If you really want to use caching then the first step is to disable that plug in so that there's a theoretical chance that someone might be served the same page twice. The second step is to only ...


1

DerfK is right about dynamic content at the full page level, you absolutely don't want cookie leakage to occur. However you can do more caching at the layers upstream - with WordPress specifically, it has a decent pluggable object cache. This means, that while the page itself won't be cached, you can store much of the database load within a ephemeral store ...


1

I don't think it should matter. The host makes this data available to the guest, via a virtual CPU/Core. I can imagine that the host can provide the guest with arbitrary values without really affecting performance that much, since it's the host that ultimately determines performance anyway. On the other hand, if KVM does bare metal virtualisation, maybe ...


1

I hope this helps any other person running Wordpress sites on Apache, I found the problem and it is nothing to do with Apache at all. The problem is that Wordpress strips out the Etag, Last-Modified, Expires and Cache-Control headers from all pages and posts. But for those wanting actual control over what can be cached and not cached that control is just ...



Only top voted, non community-wiki answers of a minimum length are eligible