Howdy again, Fixed my own problem. Squid was configured for way too many aufs threads. Thanks anyway! On 5/15/06, Dan Thomson <thomson.dan@xxxxxxxxx> wrote:
Hey all, Squid seems to be sucking up all available memory when I use aufs and I'm trying to figure out why. I was hoping someone on the list might have an answer. I've reduced the cache_mem to 200 MB (the computer running squid has 3 gig), dropped the 2 cache_dirs down to 20 MB each and turned memory pooling off. Despite this, when I run squid and request one object (around 2 kb in size) squid's virtual memory jumps to use all available memory, I get a bunch of "thread creation failed" errors and squid dies. (top right before squid dies): PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 8066 proxy 25 0 3071m 56m 2372 R 94.2 1.5 0:02.86 squid I'm assuming this is probably related to system settings. I've tinkered with them a bit (both increasing and decreasing them) but so far, no luck. I'm running this on a i386 debian machine (stable). Any help would be appreciated. Here's a little snippet from my squid.conf: # All testing values... just trying to get something working cache_mem 200 MB cache_swap_low 90 cache_swap_high 95 maximum_object_size 10 MB minimum_object_size 0 KB maximum_object_size_in_memory 10 MB store_avg_object_size 20 KB memory_pools off cache_dir aufs /var/spool/squid/1 20 10 10 cache_dir aufs /var/spool/squid/2 20 10 10 Thanks a tonne, Dan Thomson
