Comment 7 for bug 1357402

Those numbers really help a lot, thanks. Without cache affinity, we don't get as much help as we'd like when people go to a wiki and pay the price the first time. Now that we have 180k objects in the cache, after a week or so past a restart, we're ok. But of course, restarts might have once a week. :(

I agree that, once tags portlet hits, we can review it. If the most pathological cases are down under 10 seconds for load, then we probably can't justify it.

--Paul

On Aug 21, 2014, at 9:52 AM, Chris Rossi <email address hidden> wrote:

> I thought it might be useful to do some impact analysis as well. There
> is currently one community with over 1000 pages. That wiki would,
> obviously, benefit from doing something. There are 18 communities with
> over 100 and less than 1000 pages. That's not generally considered a
> huge number of objects, but object retrieval seems to be awfully
> expensive, so there may even be an impact at that level. There are 43
> communities with over 30 and less than 100 pages. 354 communities have
> more than one page and less than 30. It might be useful to look at
> performance of the one large wiki after the tags portlet change hits, to
> see if we really have a performance problem worth fixing.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1357402
>
> Title:
> Make wiki pages not load every wiki page
>
> Status in KARL3:
> In Progress
>
> Bug description:
> Shane wrote:
>
> It seems that wiki pages load the entire wiki on every page load.
> That's obviously expensive and could be low hanging fruit.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/1357402/+subscriptions