Slightly off topic - again! When profiling the different indexing functions with xdebug it produces timings for each php function - but only related to their execution order. So something like wikiFN will show up all over the place. Do you know of a simple way to get an aggregate output of all the timings of all the different calls to a particular function. Its the sort of thing that would show how many times wikiFN was called over a single page generation without having to post process the information as I see it now. I hope that makes sense. Chris > -----Original Message----- > From: dokuwiki-bounce@xxxxxxxxxxxxx > [mailto:dokuwiki-bounce@xxxxxxxxxxxxx]On Behalf Of Andreas Gohr > Sent: 15 September 2005 11:50 > To: dokuwiki@xxxxxxxxxxxxx > Subject: [dokuwiki] Capsulating file access (was: The > database question: > a new spin) > > > On Wed, 14 Sep 2005 15:02:51 +0100 > "Chris Smith" <chris@xxxxxxxxxxxxx> wrote: > > > Sort of on this topic, although most major wiki page file access is > > routed through io.php, not all is. There are large numbers of > > filemtime calls directly accessing the raw wiki page. Is it worth > > making a wrapper for filemtime and converting those filemtime calls > > for wiki data files (pages/instructions) to use it? > > We would need to have a look at all occurences of filemtime. I guess > where it is used other file modifications take place as well. But in > general it sounds like a good idea. > > Thinking of it, we should see if we can make use of some static > variables to make some of the more common functions like > wikiFN() a tick > more efficient. > > Eg. if wikiFN() would save all wikiname <-> filename pairs in a static > array it could return from that array instead of calculating the same > pathname again and again... > > I'll keep that in mind for the next release. > > Andi > -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist