Re: File map bits

From: Duane Wessels <wessels@dont-contact.us>
Date: Wed, 19 Jan 2000 09:31:03 -0700

On Tue, 18 Jan 2000, Warren Togami wrote:

> Dear List,
>
> My cache manager is currently showing this:
>
> Store Directory Statistics:
> Store Entries : 47403
> Maximum Swap Size : 10240000 KB
> Current Store Swap Size: 314062 KB
> Current Capacity : 3% used, 97% free
>
> Store Directory #0: /cache
> First level subdirectories: 16
> Second level subdirectories: 256
> Maximum Size: 10240000 KB
> Current Size: 314062 KB
> Percent Used: 3.07%
> Filemap bits in use: 47399 of 65536 (72%)
> Filesystem Space in use: 374336/15309448 KB (2%)
> Filesystem Inodes in use: 0/0 (0%)
>
> I could be wrong, but I believe Filemap bits are not supposed to go that
> high. The Squid FAQ says that ideally the filemap bits should reach 50%
> when the cache is full. I lowered my store_avg_object_size to 6 KB (Cache
> Manager reports 6.6KB mean object size) and this still does not change. I'm
> worried that this number will continue to climb and Squid will crash.
>
> SQUID.2.3.STABLE1
> Linux 2.2.14
> cache_mem 80 MB
> cache_dir ufs /cache 10000 16 256
>
> I believe I have followed the FAQ, and the Cache Manager still reports that
> abnormally high value. Am I missing something?

filemap bits are allocated dynamically in Squid-2.3. The FAQ comment is
out of date. If you look at the cache manager, you may see anywhere from
0 to 99% filemap bits in use at any given time.

Duane W.
Received on Wed Jan 19 2000 - 09:47:37 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:50:30 MST