In cache.log has some queue congestion prior to SO_FAIL appearance and
during SO_FAIL appearance:
2007/01/18 14:08:27| squidaio_queue_request: WARNING - Queue congestion
2007/01/18 14:08:30| squidaio_queue_request: WARNING - Queue congestion
2007/01/18 14:08:34| squidaio_queue_request: WARNING - Queue congestion
2007/01/18 14:08:39| squidaio_queue_request: WARNING - Queue congestion
Should I try to lower the thread number to see if that yields less
SO_FAIL?
Is there anything that I can try to improve the situation?
Thanks,
Khanh
-----Original Message-----
From: Henrik Nordstrom [mailto:henrik@henriknordstrom.net]
Sent: Friday, January 19, 2007 5:11 PM
To: Nguyen, Khanh, INFOT
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] SO_FAIL in store_log under high load
fre 2007-01-19 klockan 16:45 -0500 skrev Nguyen, Khanh, INFOT:
> 1) what has caused the swap failure? Is it due to async threads or
disk
> failure?
Anything in cache.log?
> 2) what is the optimum thread value that should one choose when
compile
> under async-io?
Depends a bit on the hardware. You have to experiment a bit. Having too
many whill cause the I/O queues to get too large, to few will make Squid
think the drive is overloaded before it is..
> 3) Is there any other parameters in the squid.conf might impact the
> ability to swap an object out to disk?
Not much.
Regards
Henrik
Received on Fri Jan 19 2007 - 16:02:26 MST
This archive was generated by hypermail pre-2.1.9 : Thu Feb 01 2007 - 12:00:01 MST