[dokuwiki] Re: increased memory footprint in recent indexer changes?
- From: Andreas Gohr <andi@xxxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Tue, 09 Oct 2007 09:10:20 +0200
TNHarris writes:
On Sun, 7 Oct 2007 21:08:49 +0200, "Andreas Gohr" <andi@xxxxxxxxxxxxxx>
said:
I noticed a lot of "out of memory messages" in my server logs since I
upgraded my wiki at splitbrain.org yesterday. They seem all to occur in
the inc/indexer.php line 71 (idx_saveIndex). I was running with 32MB
(I'm now up at 64 which seems to fix it for now).
The drawback of having a small test dataset.
It's really that splitting the index into word-length blocks allowed
individual files to be loaded into memory. That improved speed over the
piece-meal access of the single index. But speed is more important for
executing searches, not building the index.
Yes and no. We're fighting two limits in the indexer. One is the memory
limit. The other is the script execution time limit which is usally 30
seconds and may not be increased on many webhosts. So the goal is to build
an indexer which works within those limits.
Andi
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
- References:
- [dokuwiki] increased memory footprint in recent indexer changes?
- From: Andreas Gohr
- [dokuwiki] Re: increased memory footprint in recent indexer changes?
- From: TNHarris
Other related posts:
- » [dokuwiki] increased memory footprint in recent indexer changes?
- » [dokuwiki] Re: increased memory footprint in recent indexer changes?
- » [dokuwiki] Re: increased memory footprint in recent indexer changes?
On Sun, 7 Oct 2007 21:08:49 +0200, "Andreas Gohr" <andi@xxxxxxxxxxxxxx> said:
I noticed a lot of "out of memory messages" in my server logs since I upgraded my wiki at splitbrain.org yesterday. They seem all to occur in the inc/indexer.php line 71 (idx_saveIndex). I was running with 32MB (I'm now up at 64 which seems to fix it for now).
The drawback of having a small test dataset.
It's really that splitting the index into word-length blocks allowed individual files to be loaded into memory. That improved speed over the piece-meal access of the single index. But speed is more important forexecuting searches, not building the index.
- [dokuwiki] increased memory footprint in recent indexer changes?
- From: Andreas Gohr
- [dokuwiki] Re: increased memory footprint in recent indexer changes?
- From: TNHarris