Re: Re: frontpage patch for client_side.c in squid 2.2 stable 5

The box has 640 Megs of memory, and doesn't swap much (if at all). I think
I've seen it up to 2 megs worth of swap during peak useage. The drives are
17 gigs, 15 gigs per drive set for cache storage. From the normal memory
calc, 10 megs per gig, 30 gigs you 300 megs worth of memory. I'm about
twice that. It's only running squid, apache (for cachemgr), and caching
DNS. That's it. Unneeded services weren't installed. I've never seen him
have swap issues... when it was first setup, I would do 'vmstat 5' during
peek useage and si & so wouldn't move. Same holds true for when it got a
little sluggish. I think you are right about it being localized to expiring
and unlinking files though... time for more digging.

----- Original Message -----
From: John A. Lauro <jlauro@umich.edu>
To: Wayne Smith <wcsmith@myrealbox.com>
Sent: Monday, July 10, 2000 6:04 PM
Subject: Re: frontpage patch for client_side.c in squid 2.2 stable 5
<<<< SNIP >>>>
> My guess is swapping. You don't mention how much RAM you have. You
> probably need more RAM, or your RAM cache is too large. When it has
> to unlink the articles, it needs to scan the entire database, which
> normally you don't notice the slowdown if it doesn't fit in RAM
> during most activity, but when it has to scan the entire store it can
> cause major swaping if it doesn't fit.
>
> --------------------------------------------------------------------------
-
> John Lauro email: jlauro@flint.umich.edu
> University of Michigan - Flint jlauro@umich.edu
> Information Technology Services
> 303 E. Kearsley St. phone: (810) 762-3123
> Flint, MI 48502 fax: (810) 766-6805
>
Received on Mon Jul 10 2000 - 20:53:08 MDT