Hi all, I've got a 64-bit Reverse-proxy squid running on Ubuntu as of yesterday (3.0Stable13). I've got it configured how I want it as far as I can tell.
I've compiled the cache_dir null type in, and configured it as "cache_dir null /tmp", as I do not want to cache to disk on this machine at all.
I want all the data to be cached in memory, but all I'm seeing in my access.log is TCP_IMS_HIT & TCP_MISS. No TCP_MEM_HIT for anything. Now, I know TCP_IMS_HIT is ambiguous and can indicate IMS_HIT from memory or disk, but in this case where I am "cache_dir null /tmp", are these IMS_HIT coming from memory, or am I misunderstanding the 'null' type?
Also, the items that are recieving TCP_MISS are items that should be in MEM_HIT all the time, as they are loaded with EVERY page load (static menu, page structure images, etc). This concerns me, as in a ufs or aufs cache_dir, these items hit from memory....
Also, in store.log, I'm only seeing RELEASE & SO_FAIL.
I do see memory usage increasing when watching "top", which is good. I'm just curious if these indicators in the logs are something to be concerned about in this type of config.
NOTEABLE CONFIG OPTIONS:
cache_mem 28672 MB
maximum_object_size_in_memory 150 KB -- My objects are between 2KB - 20KB (so, 150 is a limit that likely should never be reached)
memory_replacement_policy heap GDSF
cache_dir null /tmp
Is this the best way to go about a memory only cache? I've seen a few posts re: using RAM disks for cache_dir instead...
Thanks All,
David
__________________________________________________________________
Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca
