Re: [squid-users] maximum_object_size > 2GB prevents caching?

On Monday 17 May 2004 09:46, Matus UHLAR - fantomas wrote:
> On 17.05 09:31, Denis Vlasenko wrote:
> > On Friday 14 May 2004 15:04, Christoph Haas wrote:
> > > this morning we found out that our cache hit ratio is zero. We started
> > > to investigate and according to the store.log all objects were tagged
> > > "RELEASE". There were absolutely no files cached in the cache_dir.
> > >
> > > We reduced the squid.conf to track down the problem. It appears that
> > > when specifying a maximum_object_size larger than 2 GB the whole
> > > caching feature becomes disabled. However I haven't seen anything
> > > useful in the cache.log that would give me a hint.
> >
> > if maximum_object_size is a 32 bit signed int, >2GB turns into negative
> > number. Certainly, it can be made 64 bit, but why do you want
> > maximum_object_size that large?!
>
> he said it was a mistake. However if someone wants squid to be able to
> cache DVD images...

Caching single 2Gb+ file flushes _an awful lot_ of other useful cached
content. Download a dozen of DVDs and your cache is effectively empty.
This will hurt.

Not to say that this is not a bug. At least squid shall just complain
"maximum_object_size must be <2Gb".

-- 
vda