Question related to #91

[mar10]

Hi,

This is a question related to #91. I did not want to mess up the discussion there:

I don't know, if this helps, but I experience a situation where I run my WebDAV server on top of Cheroot.
Benchmarks show that it is very slow compared to using Gevent.
This only occurs when uploading a lot of files using File Explorer. macOS Finder behaves way better, so it is also related to the request sequence used (see mar10/wsgidav#149).
I am not sure what exactly is happening there, but increasing the thread count helps.
When it's slow, the console output looks like timeouts every few seconds, so I figured it may be addressed by this issue
I tried with pip install git+https://github.com/cherrypy/cheroot.git@feature/91-non-blocking-sockets and setting back to 10 threads, which I think is the default. but the performance did not increase compared to Gevent.
I you think this is related to issue 91, I can send more debug info or run test versions here.
Otherwise, simply close this...

[webknjaz]

Well, it's still thread-based. Gevent is asynchronous which helps it to utilize the network better.

@mar10 try testing #199 which is a rewrite of #176/#117

[webknjaz]

So try pip install git+https://github.com/the-allanc/cheroot.git@request-based-workers

[mar10]

This is a major improvement compared to the previous runs (see this comment 3. and 4.).
Copying 300 files à 1MB, using cheroot with 10 threads:

The first 200 files get copied pretty fast, so cheroot become usable with a low thread count for me now!

Same with 100 threads does not show much of a difference:

Still not quite as fast as gevent, but anyways:

Note that the raw PUT throughput seems not to be the problem. It's more the handling of different involved WebDAV requests I assume.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[webknjaz]

@mar10 is this still relevant?

[mar10]

Did only a smoke test, but it seems to be fixed. Thanks!