Re: [squid-users] Re: Still having some slowness

On 15/02/2014 6:54 a.m., Scott Mayo wrote:
> On Fri, Feb 14, 2014 at 11:34 AM, Scott Mayo wrote:
>> On Fri, Feb 14, 2014 at 10:32 AM, Scott Mayo wrote:
>>> On Fri, Feb 14, 2014 at 10:10 AM, babajaga wrote:
<snip>
>> ------------------------------------
>> Assuming, you are logged in as root, the simplest is to edit
>> /etc/init.d/squid and insert
>>
>> ulimit -n 4096
>>
>> before the actual start comd for squid.
>>
>> Then restart squid, and the new limit should be effective.
>>
>> This also will be a permanent solution, surviving a new boot.
>> -------------------------------------------------------
>>
>> Just got that response, but had arleady edited the limits.conf file
>> and set the descriptoers to 8192 and restarted squid and now I am
>> showing:
>>
>> Maximum number of file desciprtors: 8192
>> Available number of file descriptors: 7958
>> Reserved number of file descriptors: 100
>>
>> Hopefully that will take care of that error and I will go from there.
>>
>> Thanks.
>> Scott
>
> Interesting. After making that change, I now have one of the CPUs
> that uses about 60% constantly. It switches CPUs some and sometimes
> splits the 60% between a couple of them. Also using about another 1GB
> of memory.
>
> I may cut the 8192 back to 4096 and see what happens. Going to watch
> it for a while this way though to see if the error has completely gone
> away.
>

It may be the fact you changed limits.conf. Which is global across that
machine. The extra CPU could be coming from anywhere in the system.

 The ulimit -n method recommended only alters the defaults for Squid in
a much more targeted way.

Amos
Received on Sat Feb 15 2014 - 12:12:45 MST