Re: delay pool not working right?

Thank you for your reply.

On Tue, 29 Jun 1999 00:11:46 +0800
David Luyer <luyer@ucs.uwa.edu.au> wrote:

| > Is my configuration wrong?
|
| No. However you might want to reduce the figures and see if it helps.
| You are limiting to 256000 bps of encapsulated TCP traffic for HTTP.
| It doesn't limit ICP, or DNS traffic, or TCP overheads (packet overheads,
| allowance for fragmentation, etc). You can see amazing amounts of overheads,
| and these increase a bit as you slow things down.

I have no sibling hosts configured, and DNS traffic seems so small.
So, there may be many overheads on HTTP.
I will try to measure contents of traffic there in a few days.

I tried to reduce these figures to slow things more tightly, but it
causes frequent timeouts on client browsers. I wonder if it causes
problem that I have only one child of the squid proxy, on which I
configured delay_pool. Does the aggregate buckets of delay_pool work
fine on this condition?

Another question...
My cachemgr.cgi shows

        Current: -18

What does it mean?

--
Hiroshi Takata <takata@rsi.co.jp>
Ryoka Systems Inc. Japan