Bag: Memory Hit Analysis
questnet/19971111 ruu/19970922 surfnet/19970930 uit/19971013 uninett/19971013 sv/19971017 mexcom/19971028 iif/19971113 adfa/19971029 vein/19971030 sztaki/19971029

Hot memory buffer has two major functions. First, it caches incoming (new) documents. Second it caches documents swapped in from disk as a result of a disk hit. It is not obvious what documents should be cached in memory if any. To further understand how Squid memory buffer works, we track down the memory hits that correspond to documents that were never swapped in:

When a document is retrieved from its source, it is placed into memory buffer. Later, a document is swapped out to free space for incoming requests. However, before the document content is freed from memory buffer, it may be requested by other clients. Such requests result in no swap-in memory hits that we are interested in. These hits are interesting because they show how effective memory buffer is in caching new (previously uncached) documents.


questnet: Tuesday, November 11, 1997: click for details ruu: Monday, September 22, 1997: click for details surfnet: Tuesday, September 30, 1997: click for details uit: Monday, October 13, 1997: click for details uninett: Monday, October 13, 1997: click for details sv: Friday, October 17, 1997: click for details mexcom: Tuesday, October 28, 1997: click for details iif: Thursday, November 13, 1997: click for details adfa: Wednesday, October 29, 1997: click for details vein: Thursday, October 30, 1997: click for details sztaki: Wednesday, October 29, 1997: click for details

http://www.cs.ndsu.nodak.edu
This page is maintained by Alex Rousskov (rousskov@plains.NoDak.edu).