Re: [squid-users] squid.conf cache_mem

From: Matt Anderson <manderson@dont-contact.us>
Date: Fri, 24 Aug 2001 10:19:33 -0400

That's one hell of a typo :)
Do you happen to know if there are any problems of leaving it this way or
any benefits of changing it?
When I run 'top' it looks like ther is about 256 RAM and in use is like 240
something but it's not touching SWAP space hardly at all.....
Any advice you can give me? woiuld this cache_mem statement make any kind
of difference in taht?

Your help is much appreciated !!!
----- Original Message -----
From: "khiz code" <khizcode@yahoo.com>
To: "Matt Anderson" <manderson@malys-midwest.com>
Sent: Friday, August 24, 2001 10:14 AM
Subject: Re: [squid-users] squid.conf cache_mem

> well that line is valid only if u have ateast ten times that amnt of
> RAm as specified in cache_mem line ;-) just joking
>
> well it seems to be a typo
> must be something like
> cache_mem 8 MB
> or cache_mem 48 MB
>
> rgds
>
> --- Matt Anderson <manderson@malys-midwest.com> wrote:
> > Ok, here is my stupid question :). My production squid server was
> > set up by a contractor and I'm trying to figure out how he's got it
> > set up so if it ever breaks I can fix it or what not. I notice in
> > the squid.conf there is this statement .... something looks a little
> > fishy to me -- is this a normal statement? Thanks!
> >
> > If it's not normal will this cause problems? Is it something I
> > should change? Should I never call this contractor again ;)?
> >
> > # TAG: cache_mem (bytes)
> > # NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS
> > # SIZE. IT PLACES A LIMIT ON ONE ASPECT OF SQUID'S MEMORY
> > # USAGE. SQUID USES MEMORY FOR OTHER THINGS AS WELL.
> > # YOUR PROCESS WILL PROBABLY BECOME TWICE OR THREE TIMES
> > # BIGGER THAN THE VALUE YOU PUT HERE
> > #
> > # 'cache_mem' specifies the ideal amount of memory to be used
> > # for:
> > # * In-Transit objects
> > # * Hot Objects
> > # * Negative-Cached objects
> > #
> > # Data for these objects are stored in 4 KB blocks. This
> > # parameter specifies the ideal upper limit on the total size of
> > # 4 KB blocks allocated. In-Transit objects take the highest
> > # priority.
> > #
> > # In-transit objects have priority over the others. When
> > # additional space is needed for incoming data, negative-cached
> > # and hot objects will be released. In other words, the
> > # negative-cached and hot objects will fill up any unused space
> > # not needed for in-transit objects.
> > #
> > # If circumstances require, this limit will be exceeded.
> > # Specifically, if your incoming request rate requires more than
> > # 'cache_mem' of memory to hold in-transit objects, Squid will
> > # exceed this limit to satisfy the new requests. When the load
> > # decreases, blocks will be freed until the high-water mark is
> > # reached. Thereafter, blocks will be used to store hot
> > # objects.
> > #
> > # The default is 8 Megabytes.
> > #
> > cache_mem
> >
>
4848484848484848484848484848484848484848484848484848484848484848484848484848
48484848484848484848
> > MB
> >
> >
> >
> > Matt Anderson
> > MCSE, CNE, CCNA, Network+
> > Network Engineer
> > Maly's Corporate Headquarters
> > (616) 956-2246
> >
>
>
>
Received on Fri Aug 24 2001 - 08:23:18 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:54 MST