Henrik, Sorry for the late reply, I've changed the cache_mem to 250MB and I am monitoring the growth. The server does have 6GB of RAM. The swap is small based on SuSE recommendations but I can add swap if necessary. Last night the squid proc grew to over 2GB so I lowered the cache_mem and restarted squid to free the 2GB. The current size is 765MB and I'm hoping it will level off at just over 1GB. If it continues to grow beyond 2GB then I'm guessing it's the malloc issue. "dlmalloc" isn't an option, as I understand it, as it is limited to 2GB. Know of any good 64bit compatible mallocs? Thanks, Dave -----Original Message----- From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Thursday, March 08, 2007 5:50 PM To: Dave Rhodes Cc: squid-users@xxxxxxxxxxxxxxx Subject: RE: Oom-killer and Squid tor 2007-03-08 klockan 13:55 -0500 skrev Dave Rhodes: > Any idea what would make the heap keep growing? You have a cache_mem of 1 GB, plus 60 GB of cache_dir. That alone is about 1.6GB or memory. Then your OS need some.. How much memory do the server have? In a previous post you claimed 6GB. Why then only 2GB of swap? If you have swap it should be at least as large as the memory, preferably larger.. but I do not think this is your problem.. If you suspect there is a memory problem with Squid then monitor the process size over time, and also see the cachemgr memory page to see if there is any indications to what the memory is being used for. And the general runtime info page as well (even if many numbers there break down when the process grows above 2GB due to glibc mallinfo reporting limitations, not our fault). Regards Henrik
