W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 1999

Re: cache policy

From: Raymond Racine <ray@malema.com>
Date: Mon, 21 Jun 1999 11:26:44 -0400 (EDT)
Message-ID: <376E5A6E.A602A156@malema.com>
To: Yves Lafon <ylafon@w3.org>, "www-jigsaw@w3.org" <www-jigsaw@w3.org>
I am inferring the you are referring to Jigsaw's LRU caching of resource
meta information and not the resource itself.  This resource information is
fundamentally some meta information that is part and parcel to the
HTTP/1.0/1.1 protocols.

Does Jigsaw cache recently served HTML?  If I call the same HTML page thrice
in succession does Jigsaw serve a cached (ignoring time out / expirations)
HTML page each time or does it read in the HTML file via file I/O calls each
time and therefore depends on the OS to buffer/cache disk I/Os.  I did not
find this kind of caching of the resource itself (HTML file) inside Jigsaw,
just the caching resource meta information (resource size, MIME type etc..)
in the source code.



Yves Lafon wrote:

> On Sat, 19 Jun 1999, Qiang Lv wrote:
> > Hi Yves,
> >
> > Can you explain the cache policy which Jigsaw uses for me? You know it
> > is hard to read source code:)
> Jigsaw uses a LRU-threshold policy.
> Only the resource with a size < cache_size * file_ratio are cached (if
> possible, of course).
> Also, when the cache is full, it tries to free the least recently used
> entries. Those entries are stored in 10 "generations" and moved back to
> the last one when used.
> Also, we plan to implement other cache policies at some point, and other
> cache related things (we currently have ICP and multicast ICP).
> Regards,
>       /\          - Yves Lafon - World Wide Web Consortium -
>   /\ /  \        Architecture Domain - Jigsaw Activity Leader
>  /  \    \/\
> /    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org
Received on Monday, 21 June 1999 11:27:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:34 UTC