some point of view: 1, the interim cache is the cache for the data stored in storage.config defined devices, same as ram cache, that means if on object is removed(overwritten) from the storage devices, it is removed from both interim-cache and ram-cache, that is very critical ensure procedure for data consistency. 2, the object maybe promote to ram-cache and interim-cache, that depends on your testing case, that means, if you batch load some uniqued files with your test tool, that will not help LRU to get the replacement works like real worlds. 3, clfus will try to cache the small files instead of the big files, which may introduce more complex in your situation. 4, if you want to test the feature function, I’d advice that you make your test urls really small, and limit the ram cache to only cache a few size limited objects, and limit the test requests to see how the object is stored in the ram interim and storage. 5, jtest is a good random cache testing tool for you to generate some testing on storage and cache 6, the interim cache is working just like the storage devices, same as a log based journal file system. 7, there is a proxy.process.cache.interim.read.success stat to count all interim cache hits
> 在 2015年2月4日，上午4:45，Acácio Centeno <acacio.cent...@azion.com> 写道： > > Hello, > > We've being performing some cache tests and noticed two issues that we > would like to check with the community: > > 1. The interim cache is limited to the same size as the RAM cache, no > matter how big the partition allocated to it is. > > 2. Whenever a volume gets full and the write head begins writing to the > volume's start again, the RAM cache gets unused for a while, and requests > that could be served from RAM get served from the storage. Notice that we > considered the possibility that the objects that we _thought_ were in the > RAM had been replaced, but even requesting the same set of objects a few > times would not make them be served from the RAM. > > Are these statements correct? We came to them based on observations made > during the tests fully described on [1]. We hope there's enough information > on the document to reproduce the tests. > > We're available should someone need more info about our test scenarios. > Feel free to contact me or Daniel Biazus at daniel.bia...@azion.com . > > [1] > https://drive.google.com/file/d/0B_pQbXm7hKZ4X2VSbXQxN1BOaEU/view?usp=sharing > > Acácio Centeno > Software Engineering > Azion Technologies > Porto Alegre, Brasil +55 51 3012 3005 | +55 51 8118 9947 > Miami, USA +1 305 704 8816 > > Quaisquer informações contidas neste e-mail e anexos podem ser > confidenciais e privilegiadas, protegidas por sigilo legal. Qualquer forma > de utilização deste documento depende de autorização do emissor, sujeito as > penalidades cabíveis. > > Any information in this e-mail and attachments may be confidential and > privileged, protected by legal confidentiality. The use of this document > require authorization by the issuer, subject to penalties. - Yongming Zhao 赵永明
