From: Reini U. <ru...@x-...> - 2001-11-12 20:24:32
|
Gary Benson schrieb: > > On Fri, 9 Nov 2001, Reini Urban wrote: > > > you probably mean to sore only xhtml and not the wiki markup in the db? > > hmm, weird idea. > > Store wiki markup and the html _after templating_ so all it has to do > for browse pageviews is select and send. I think it was Jeff you answered on this suggestion of mine earlier this year: http://phpwiki.sourceforge.net/phpwiki/index.php?PerformanceHacks "Change/rerender the html when a referred page is deleted or added. Do as much as possible in the editpage post step. Maybe check timestamps of the templates and gettext messages, which influence the rendering also, but better is to dirty all pages in the admin mode with a seperate button. => IMHO the HTML rendering is negligible compared to the database access. It would be much more important to cache complete pages in the filesystem and update them if templates or anything else has changed. Minimizing database access is much more important than code optimization." So we could add some admin code to update or dirty wiki pages when templates and php code change. This would lead to a faster caching code (=> 302), but would require another wikipage flag. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |