>There are a few standard suggestions that can be made, but they pretty
>much amount to using the appropriate rc.* file. Other than that, it
>becomes something like the story of the refigerator repairman: "$5 for
>hitting it, $95 for knowing _where_ to hit it." It really takes a lot
>of experience to do this quickly -- and even despite that, finding the
>OPTIMUM settings for unusual configurations requires repeated
>experiments.
>
>You shouldn't hold this against the phone support folks, it's really
>outside their job description.
Perhaps, but it's not outside OUR job descriptions! I.e. the site
contacts who are asking for the support! If 95% of the job is
in knowing where to hit it then writing a chapter or book about
the internals of the cache manager and how to tune it would help
your customers do THEIR jobs better, which would mean greater
customer satisfaction for their user communities, thereby improving
sales, etc, etc.
-Mitch
--
"Families can't trust Disney"
