Santiago del Castillo wrote:
Hi, sry, when I said maximum_object_size I wanted to say maximum_object_size_in_memory :P.

Right now (i don't know how) it's working. Here is some info:

Cache information for squid:
    Request Hit Ratios:    5min: 92.0%, 60min: 92.3%
    Byte Hit Ratios:    5min: 35.5%, 60min: 34.7%
    Request Memory Hit Ratios:    5min: 61.6%, 60min: 60.2%
    Request Disk Hit Ratios:    5min: 0.5%, 60min: 0.4%

Memory usage for squid via mallinfo():
    Total space in arena:   79176 KB
    Ordinary blocks:        71934 KB   9224 blks
    Small blocks:               0 KB      0 blks
    Holding blocks:           432 KB      2 blks
    Free Small blocks:          0 KB
    Free Ordinary blocks:    7241 KB
    Total in use:           72366 KB 91%
    Total free:              7241 KB 9%
    Total size:             79608 KB


It's very VERY good compared with I was getting before.


My box is a P4 3.0 with 4 GB RAM under FedoraCore 5.


Cheers and thanks,
Santiago del Castillo


For what it's worth (and last I read), Squid only stores fetched-from-the-source objects in memory. Once an object has been flushed to disk (like on shutdown) it will not pull subsequent CACHE_HITS in to the memory cache.

Hence the suggestion of letting the OS use the majority of memory for disk caching.

Chris

Reply via email to