RE: [squid-users] ...Memory-only Squid questions

Glad to help David, please let us know how it progresses.
 
Dont know if you saw this in the archives: http://www.mail-archive.com/squid-users@squid-cache.org/msg19824.html but it might help guide you on your SO_FAIL issue. It might be worth moving to LRU and establishing a baseline of performance (using either SNMP+cacti or cachemgr) before moving to fancier replacement policies. Personally, I would go 'store_log none' and not worry about it unless you see something in cache.log
 
The best all around advice I can give on Squid is to start simple! Once everything works the way you expect, then start tweaking your way into complexity with a means to track the (in)effectiveness of each change you make (and a known good configuration that you can always go back to when you inevitably fubar the thing!).
 
- Gregori

________________________________

From: David Tosoff [mailto:dtosoff_at_yahoo.com]
Sent: Mon 4/6/2009 8:46 PM
To: squid-users_at_squid-cache.org; Chris Robertson
Subject: Re: [squid-users] ...Memory-only Squid questions

Thanks Chris.

I had already read both of the wiki post and the thread you directed me to before I posted this to the group.

I already had compiled heap into my squid before this issue happened. I am using heap GDSF. And, I wasn't able to find "--enable-heap-replacement" as a compile option in './configure --help' ... perhaps it's deprecated?? Is it a still a valid compile option for 3.0 stable 13?

In any event, a gentleman named Gregori Parker responded and helped me with some suggestions and I've managed to stabalize the squid at ~20480 MB cache_mem

The only thing I seem to be missing now is the SO_FAIL issue.
Correct me if I'm wrong, but I assume 'SO' stands for 'Swap Out'... But how does this affect a system where there is nowhere for the squid to swap out to (cache_dir null /tmp)...?

Thanks for all your help so far.

Cheers,

David

--- On Mon, 4/6/09, Chris Robertson <crobertson_at_gci.net> wrote:

> From: Chris Robertson <crobertson_at_gci.net>
> Subject: Re: [squid-users] ...Memory-only Squid questions
> To: squid-users_at_squid-cache.org
> Received: Monday, April 6, 2009, 4:56 PM
> David Tosoff wrote:
> > Hey all, haven't heard anything on this and could
> really use some help. :)
> >
> > You can disregard the HIT related questions, as once I
> placed this into a full scale test, it started hitting from
> memory wonderfully (~40% offload from the origin)
> >
>
> Good news...
>
> > The config works great, to a point. It fills up my
> memory up, but keeps going way past the
> "cache_mem" that I set.
>
> http://wiki.squid-cache.org/SquidFaq/SquidMemory
>
> > I've dropped it down to 24GB, but it chews up all
> the memory on the system (32GB) and then continues into the
> swap and chews that up too. At that point, squid hangs,
> crashes then reloads and the cache has to spend another few
> hours building everything up into memory again. Like I said
> though, it works great...until the mem is full...
> > I'm now going to test with a 4GB cache_mem and see
> what she does.
> >
> > Can anyone offer any suggestions for the best, most
> stable way of running a memory-only cache? is 'cache_dir
> null /tmp' actually what I want to be using here?
>
> Yes.
>
> > The SO_FAIL's concern me, but I'm not sure if
> they should?
> >
>
> Perhaps
> http://www.mail-archive.com/squid-users@squid-cache.org/msg19824.html
> gives some insight. Are you using a
> (cache|memory)_replacement_policy that you didn't
> compile support for?
>
> > Thanks!
> >
> > David
>
> Chris

      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
http://ca.toolbar.yahoo.com <http://ca.toolbar.yahoo.com/> .
Received on Tue Apr 07 2009 - 05:05:55 MDT