Hi all!
As we're seeing more and more https on ftp.acc.umu.se I've noticed
that the number of threads listed as state W in server-status has
skyrocketed.
From 2-4 threads busy using http we're talking 70-100 threads for the
same bandwidth when the machine is pushing a mighty 2.7% average CPU
load.
This is on a large-file workload, serving plain files.
I anticipated a few more threads due to ssl, but for slow downloaders
I would expect connections doing async write and mostly waiting for
the bits to dribble through the Internet Tubes inbetween the
occational wakeup to do ssl&send...
Are we not doing async write completion at all on https/ssl and
falling back to the old worker behaviour of one thread per connection?
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [email protected]
---------------------------------------------------------------------------
At last I'm organized", he sighed, and died.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
