Thanks for the tips, I will test this and come back with the result.
/ E
Original Message ---
On Wed, 18 Jun 2008 13:24:52 -0700
Michael S. Fischer [EMAIL PROTECTED] wrote:
On Wed, Jun 18, 2008 at 4:51 AM, Rafael Umann
[EMAIL PROTECTED] wrote:
If it is a 32bits
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes:
1. The 32bits arch (cant open threads and the storage file is too
small), so im moving into 64bits.
Yes, 32bit is generally not big enough to Varnish for non-trivial
workloads.
2. The cpu usage of the listener process with 2 hits/sec
* Oliver Oli
| are there any debian buildpackage scripts available?
Yes, you get them in the debian/ directory if you do a subversion
checkout.
--
Tollef Fog Heen / Linpro ASt: 21 54 41 73
UNIX is user friendly, it's just picky about who its friends are
how about your storage file size?
[]s,
On Mon, 23 Jun 2008 21:20:59 +0200
Erik Torlen [EMAIL PROTECTED] wrote:
I still have the same problem :(
The threads are created up to 238 where they are stopped, even if I
set threads_max = 1000 and threads_pools = 2 (or 3).
I also tested the tips
In message [EMAIL PROTECTED], Erik Torlen writes:
I still have the same problem :(
The threads are created up to 238 where they are stopped, even if I set
threads_max = 1000 and threads_pools = 2 (or 3).
I also tested the tips and decreased the stack sixe to 512 and increased
overflow_max to
We are testing varnish as a potential replacement for our legacy squid
setup on a dual core 8GB RAM server. We've noticed that varnish
performance would suddenly deteriorate after running for a while. The
server load is at around 0.2 before all of a sudden it climbs to over
20 and keeps rising.