Hey everybody,
We still have a few open RC bugs which should be solvable given a few
days each with a dedicated researcher. They are all blocking 3.1 release
and some are causing major headaches to users of 3.0.
2305 - auth assertions (under refcounting?)
2424 - FD 'leaks' due to auth
After analyzing a large cache with significantly declining hit ratio
over the last months I have came to the conclusion that the removal of
cache deny QUERY can have a very negative impact on hit ratio, this due
to a number of flash video sites (youtube, google, various porno sites
etc) who
2008/12/1 Henrik Nordstrom [EMAIL PROTECTED]:
After analyzing a large cache with significantly declining hit ratio
over the last months I have came to the conclusion that the removal of
cache deny QUERY can have a very negative impact on hit ratio, this due
to a number of flash video sites
mån 2008-12-01 klockan 09:40 -0500 skrev Adrian Chadd:
Hm, thats kind of interesting actually. Whats it displacing from the
cache? Is the drop of hit ratio due to the removal of other cachable
large objects, or other cachable small objects? Is it -just- flash
video thats exhibiting this
Hi,
I am trying to add extension to ICAP layer in squid 3.0 STABLE 10.
Our service works both in respmod and reqmod, in some cases we know
right after reqmod that the data should passed directly to the client.
in those cases we like to be more efficient by not utilizing respmod at
all, sending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Nordstrom wrote:
After analyzing a large cache with significantly declining hit ratio
over the last months I have came to the conclusion that the removal of
cache deny QUERY can have a very negative impact on hit ratio, this due
to a number
mån 2008-12-01 klockan 11:00 -0500 skrev Tres Seaver:
Having a single recommended config seems dubious: I for one never
run squid as a forward proxy, for instance. We should probably split
apart the default / recommended forward and reverse configurations
(which are just starting points,
Amos Jeffries wrote:
Hey everybody,
We still have a few open RC bugs which should be solvable given a few
days each with a dedicated researcher. They are all blocking 3.1 release
and some are causing major headaches to users of 3.0.
2305 - auth assertions (under refcounting?)
2424 -
Isn't the real question who called FwdState::complete()? It's only meant
to be called when all data has been placed into the entry, not before..
tis 2008-12-02 klockan 00:56 +1300 skrev Amos Jeffries:
revno: 9386
committer: Amos
mån 2008-12-01 klockan 09:40 -0500 skrev Adrian Chadd:
Hm, thats kind of interesting actually. Whats it displacing from the
cache? Is the drop of hit ratio due to the removal of other cachable
large objects, or other cachable small objects? Is it -just- flash
video thats exhibiting this
tis 2008-12-02 klockan 12:35 +1300 skrev Amos Jeffries:
A global blockade is a little harsh when it's only a few offenders.
If we can locate a pattern to match just these sites while any dialog is
going on I'd be happy to support a reversal for just them. That would keep
most of the main
Amos Jeffries wrote:
Hey everybody,
We still have a few open RC bugs which should be solvable given a few
days each with a dedicated researcher. They are all blocking 3.1 release
and some are causing major headaches to users of 3.0.
2305 - auth assertions (under refcounting?)
2424 -
Isn't the real question who called FwdState::complete()? It's only meant
to be called when all data has been placed into the entry, not before..
I started with that idea, but the code proved to be very convoluted.
On an error the FTP engine calls ftpFail(), which syncs down to
Hmm. Given that heap GDSF out-performs LRU in the common case, and
there's a crashing bug in LRU at the moment anyway, maybe the best
thing to do is to change the default replacement policy -- and always
compile in the heap algorithms?
On 02/12/2008, at 2:05 AM, Henrik Nordstrom wrote:
14 matches
Mail list logo
