mån 2006-09-18 klockan 16:40 -0700 skrev Pranav Desai:
> Could any of the above have any impact on the performance.
Well.. it's a sign that your cache_dir is probably overloaded, or that
you have set cache_swap_high too high making it overly hard for the LRU
garbage collection to keep up.
Regard
On 9/19/06, Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote:
> >m?n 2006-09-18 klockan 10:31 -0700 skrev Pranav Desai:
> >> I am running some polymix-4 tests with squid 2.6-S3. Every single test
> >> I have run so far has these warning. Some FAQs and other searches
> >> suggest that this is caus
> >m?n 2006-09-18 klockan 10:31 -0700 skrev Pranav Desai:
> >> I am running some polymix-4 tests with squid 2.6-S3. Every single test
> >> I have run so far has these warning. Some FAQs and other searches
> >> suggest that this is caused by a corrupted swap.state, and the
> >> solution is to wipe o
On 9/18/06, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
mån 2006-09-18 klockan 10:31 -0700 skrev Pranav Desai:
> I am running some polymix-4 tests with squid 2.6-S3. Every single test
> I have run so far has these warning. Some FAQs and other searches
> suggest that this is caused by a corrupted
mån 2006-09-18 klockan 10:31 -0700 skrev Pranav Desai:
> I am running some polymix-4 tests with squid 2.6-S3. Every single test
> I have run so far has these warning. Some FAQs and other searches
> suggest that this is caused by a corrupted swap.state, and the
> solution is to wipe out the cache d
Hello All,
I am running some polymix-4 tests with squid 2.6-S3. Every single test
I have run so far has these warning. Some FAQs and other searches
suggest that this is caused by a corrupted swap.state, and the
solution is to wipe out the cache dirs and rebuild the cache.
Is there a better solut