andersb at vgnett.no
Sat Aug 5 23:07:28 CEST 2006
> W nbr 34 sess 0x16c1008 fd 158 xid 2017851670 step 7 handling 128 age 8555
> W nbr 34 sess 0x1b3f008 fd 173 xid 2018914270 step 9 handling 64 age 5960
> W nbr 29 sess 0x1902008 fd 80 xid 2019001809 step 7 handling 128 age 5729
> W nbr 41 sess 0x1ef7008 fd 319 xid 2019426763 step 7 handling 128 age 4648
> W nbr 35 sess 0x1c7f008 fd 45 xid 2019626419 step 7 handling 128 age 4174
> W nbr 39 sess 0x1feb008 fd 264 xid 2019738777 step 1 handling 4 age 3893
> This bugs me a bit, clients which for some reason or other does not
> pick up their document, but which leaves the TCP connection stalled.
Ouch. Can you see if Opera is overrepresente in those? I see some funny
behavior from Opera in my work, but it may be just a different
implementation of HTTP/1.1 than Firefox and IE, and still a be after RFC
> sendfile() has no way to specify a timeout. I may have to find a way
> to kill these worker threads with violent means.
I guess there is no way round it. Would it make any difference if it was
kernelspace and not userland?
More information about the varnish-dev