Re: Squid store replacement policies

On Thu, Apr 27, 2000, Alex Rousskov wrote:

> > > The "hot object cache" policy indexes StoreEntries (that may have
> > > MemoryObject structures). What is removed when you purge the "hot object
> > > cache" is the StoreEntry. It is removed from the "hot memory index"
> > > leaving "file store index" and its entries unchanged.
> >
> > Again no. The "hot object cache" currently indexes MemoryObjects which
> > happens to have a StoreEntry. A StoreEntry cannot be indexed by the "hot
> > object cache" if it doesn't have a MemoryObject.
>
> I was describing how the things may be organized, not how they work now.
>
> > The "hot object cache" is not at all implemented as a FS type store. It
> > is completely different almost all aspects. It simply piggy-backs on
> > Squids object forwarding.
>
> Exactly. And, IMO, that is not the best design possible.

.. and its going to change. I do not like the current code at all, and once
I've got my modio code into the main squid tree I'll move onto reworking
the 'hot object cache' as part of the storage manager rework for
asyncio.

Deciding which 'pages' inside which objects get freed when memory is running
short is something I've been thinking about for a while. I'll be thinking
about this in more depth (and be in a position to give more feedback :)
as soon as the current modio code has been imported.

Adrian
Received on Thu Apr 27 2000 - 15:36:08 MDT