On 10/6/05, Harry Fuecks <hfuecks@xxxxxxxxx> wrote: > OK - well 100% CPU usage on the server could be related although I > assume people are experiencing a client-side problem here - the > browser keeps saying "page loading" - so these are two seperate > problems. > > Looking at the indexer it already has a mechanism make sure only one > indexer runs at any given time, by using a "lock" directory. > > Attached is an updated version of indexer.php (./lib/exe/indexer.php) OK. This new version fixes the problem for me. Thanks. Bin > which flushes the image first along with headers that should get the > browser to drop the connection as soon as it's received the whole > image. Indexing (if needed) then happens after this. > > Haven't tested it extensively but it looks good so far (both Firefox > and IE drop the connection immediately). Another possible optimization > would be to check whether indexing the page is actually needed before > require_once is called - should reduce the effort PHP has to make. > > It's possible that keeping the connection open was part of the problem > causing high CPU usage but it's probably not worth guessing until so > hard figures are available (e.g. profiling) > > Anyway - will drop a copy of this script to Andy via darcs. > > > On 10/6/05, Christoph Schindler <hop@xxxxxxxxxxxx> wrote: > > On Thu, Oct 06, 2005 at 10:48:05AM +0200, Harry Fuecks wrote: > > > When people are saying "it's slow to load", do you mean the browser > > > keeps say "page loading"? > > > > That and the cpu usage goes up to 100% for several seconds. If you load > > another page during the time, it takes even longer, and so on.. until > > you have a couple dozen apache-threads that each uses a view % of the > > cpu. > > > > Later today I'll finally have the time to look into it. > > > > hop > > > > -- > > DokuWiki mailing list - more info at > > http://wiki.splitbrain.org/wiki:mailinglist > > > > > -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist