A quick start
might be to temporarily disable all checking
of links, and see if that helps much.
This seems to be a helpful suggestion. Without profiling, it's
hard to tell where the bottleneck is, but I think link checking
is a good guess.
It's more than a guess--one of the very first things we did
to test the new software is to run bots to fetch lots of pages,
which we then sorted by response time. The pages that sank to
the bottom of that list were special pages with complex queries
and long pages with lots of links. Long pages without many links
were not a problem.
I just did an ad-hoc benchmark on Piclab of the same installation
with and without link-checking, and on the limited set of pages
used by the test suite, the speedup was only about 3%. Of course
all benchmarks on single-servers may be less applicable to the
multiple-server installation we're going to have soon.
--
Lee Daniel Crocker <lee(a)piclab.com> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC