On 9/8/06, Henrik Nordstrom <henrik@xxxxxxxxxxxxxxxxxxx> wrote:
fre 2006-09-08 klockan 15:55 -0700 skrev Pranav Desai: > The other thing I found is in the strace. Last brk() before it failed. > It seems like some 24bit limit. Any ideas ? I have only seen such limits on 32-bit systems. Never on an 64-bit system running 64-bit software. So triple-check that ulimit is set like you expect for the Squid process. Remember that ulimit is per process so only because your shell says something large does not neccesarily mean that Squid is running under the same ulimit.
Interestingly, disabling dlmalloc solved all the problems. Now the process size can grow in excess of 2 GB. Other than maybe some performance gain, do I lose anything by disabling dlmalloc ? Thanks for all your input. -- Pranav
The Squid I am currently watching is now close to 4GB in size. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 20701 squid 15 0 3931m 3.8g 1532 S 4 32.4 528:02.21 squid and still climbing (cache not full yet). This is on a stock Ubuntu dapper x86_64 with a custom Squid-2.6.STABLE3 build (some Squid patches, none relevant to memory limits). Regards Henrik
-- ------------------------------ http://pd.dnsalias.org
