On Thu, Jul 29, 2010 at 4:07 PM, Strainu <strainu10(a)gmail.com> wrote:
Could you please elaborate on that? Thanks.
When pages are parsed, the parsed version is cached, since parsing can
take a long time (sometimes > 10 s). Some preferences change how
pages are parsed, so different copies need to be stored based on those
preferences. If these settings are all default for you, you'll be
using the same parser cache copies as anonymous users, so you're
extremely likely to get a parser cache hit. If any of them is
non-default, you'll only get a parser cache hit if someone with your
exact parser-related preferences viewed the page since it was last
changed; otherwise it will have to reparse the page just for you,
which will take a long time.
This is probably a bad thing. I'd think that most of the settings
that fragment the parser cache should be implementable in a
post-processing stage, which should be more than fast enough to run on
parser cache hits as well as misses. But we don't have such a thing.