Me again. The fact is that with large databases, a massive improvement can be seen from avoiding the scans in Pages.pm.
As far as I can tell that scan is being done for any skin whatsoever, even if the statistics info is not being used after it was generated. If some people experience skin- or browser-related performance issues, I would guess they be caused by something different, so we should be careful not to mix up those two matters here. I have not seen hangs from HTML delivery with certain browsers or skins yet, but if that is the case, I would point to something like HTTP version differences. HTTP/1.1 is able to do pipelining, BTW. There are settings in Firefox and Mozilla to influence that behaviour, so one could try that. Also, there are PERL tricks for buffering HTTP headers vs. data correctly, as is explained here: http://httpd.apache.org/docs/1.3/misc/FAQ.html#premature-script-headers Normally, this should be handled transparently by standard libraries like CGI.pm, but I don't know if the code is self-made or reused. -- meyergru _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
