Thomas Dalton wrote:
After strugling some time with the profiler (my debugfile never showed any content) I tried the Eaccelerator knowing this might (not) be the answer. But it was. It increased the speed significantly, whatever the cause was. Thanks!
You're probably just hiding the problem, though. Eaccelerator will just speed up viewing pages that have already been parsed, it won't speed up viewing pages for the first time (and that's first time for each logged in user, I expect, so the difference may be minimal if you test with other accounts).
This is completely incorrect, eAccelerator does nothing of the kind. It is a bytecode cache, and as such works in the same way as the bytecode cache we usually recommend: APC. It doesn't cache pages, it caches compiled source code. This is undeniably a good thing.
You can store the parser cache in eAccelerator instead of in the database, but the performance improvement from that would be small if anything, Ruud has not done it, and nobody has recommended that he should.
-- Tim Starling