[Varnish] #85: High number of "worker threads not created" and "overflowed work requests"

[Varnish]

#85: High number of "worker threads not created" and "overflowed work requests"
----------------------+-----------------------------------------------------
 Reporter:  Thias     |        Owner:  phk
     Type:  defect    |       Status:  new
 Priority:  normal    |    Milestone:     
Component:  varnishd  |      Version:  1.0
 Severity:  normal    |   Resolution:     
 Keywords:            |  
----------------------+-----------------------------------------------------
Comment (by phk):

 It really depends on the traffic Varnish receives, but 3G is nothing out
 of the ordinary.

 The other side of this is that a failure to create a workerthread is not
 necessarily a bad thing in Varnish.  The request will just be queued for
 when another workerthread becomes available.

 Check with varnishstat(1) how many threads it manages to create, and check
 with varnishhist(1) what your response time looks like.  As long as your
 responsetime is fine, it doesn't matter of some requests are a bit slow.

 On the other hand, if you have many slow clients and large objects, you
 will tie up a lot of worker threads, and there is no way around it in
 Varnish.  (... right now.  I have been thinking of ways to address that,
 but nothing sensible has presented itself yet).

 If you're trying to put varnish in front of a really heavy web-service, 64
 bit is probably the only way to get the necessary space for both storage
 and worker threads.

 Poul-Henning

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/85>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator