Re: squid-novm and squid

Adrian Chadd wrote:

> Any hints why? I'd rather not try to find the relevant messages in amongst
> the archives..

Because the old memory manager locked in-transit objects fully in
memory. It could not "swap in on demand" like the current one. It was
primarily memory based. The design was then changed to see the disk as
the "primary" source, and memory a voilatile resource.

Notes:

You should probably separate on hot-cache and in-transit objects. The
usage pattern of the two is quite different, and it is not good if
in-transit "always" flushes the hot-object cache like it is done today..

The complicated in-transit case is when there is two clients listening
to the same large object (thing ISO image or other objects hundreds of
MB in size) at different speeds. How to decide on what parts of memory
to reclaim for other uses until the second client catches up?

/Henrik
Received on Wed May 03 2000 - 14:01:40 MDT