[dokuwiki] Re: Performance and caching
- From: Harry Fuecks <hfuecks@xxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Thu, 8 Sep 2005 02:51:01 +0200
> Upon page update/creation/etc., all you have to do is expire the cache for
> the pages that have dependencies on the page being modified."
and
> If DokuWiki knows which pages are made obsolete by an event, it can always
> invalidate the cache files for those pages, forcing them to refresh on next
> load."
Where this can be problematic is managing the relationships /
dependencies between pages. If it's just the links then perhaps that's
doable. But there are also plugins around for things like "includes"
and the danger is needing alot of code to handle it.
> It really isn't an issue to live with pages that are stale by minutes. The
> only users who are going to know the difference are those that just created
> or deleted a page -- and possibly only if they're not logged in. They'll
> need to be aware of the staleness interval. But you can even hide that a bit
> by freshening the HTTP referrer ("referer") page and any backlinks DokuWiki
> is aware of.
That's probably the easier way to go. Also, although there's still the
dependancies problem, just for links it may be fairly resource
friendly to check whether links are up to date before serving the
cached version.
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
Other related posts:
