Re: [squid-users] throughput limitation from cache

Hi,

Also sprach Jason Healy <jhealy+squid@logn.net> (Thu, 12 Jan 2006
21:23:38 -0500 (EST)):
> At 1137138557s since epoch (01/12/06 20:49:17 -0500 UTC), Richard
> Mittendorfer wrote:
> > It's even if I'm the only client and it's one big file that's
> > retrieved, so it must be some kind of internal limit. I have to look
> > into the source, maybe I can find it hardcoded somewhere. 256kB/s
> > looks so artificial ;)
>
> Not too sure about that. I just downloaded a non-cached file through
> our proxy and broke to 270KB/s (this is the busiest time of day for
> us, though). I know I've done better than that when it's quiet.
>
> If I turn around and request the same file again (now that it's
> cached), I'm pulling >2.0MB/s without any trouble.

Well, can't reach this here. Cached ~260KkB/s. And I'm quite sure the
file was still in the linux disk cache. What does your cache_dir looks
like? aufs I assume.

Since you've got plenty of RAM - maybe this is the reason? Or it's some
kind of autotuned by download speeds? Can't think of.

> We're on a P3-850MHz with 1.5GB RAM and 30GB SCSI RAID1. I'm hoping
> to upgrade by the end of the month. ;-)

This box is up 24/7 and it's an allrounder for a few people in our SOHO
(here for SOcial HOming) :). The little Celi + Mobo + raid0scsi just
draws about 50/60 watts. The IDE HD's that carries the storage are spun
down most of the time. With power consumption of a modern processor in
mind, I'm quite happy with it. ;)
    
> > Had a look at it. Doesn't look like debian's squid is compiled with
> > async-io. ..hmm - <coffee> - sure, debian's is async-io. Must
> > be. aufs _is_ compiled in: --enable-storeio=ufs,aufs,diskd,null
>
> Confirmed that it has it. We're on a stock config of Debian 3.1:
>
> # squid -v
> [...]

Jupp.

> Jason

sl ritch
Received on Thu Jan 12 2006 - 19:56:52 MST