MichaIng

This has now been merged here: https://github.com/cherrypy/cheroot/pull/401 Testing/verifying the idle CPU usage benefits would be welcome. On Windows systems, sadly a capped timeout needs to stay, as the connection handler...

You might want to try CherryPy

Yes, I checked back what the reason for us was to stick with CherryPy

With https://github.com/cherrypy/cheroot/pull/352 it would then be the `expiration_interval` that can be set for the `HTTPServer` class already and defaults to 0.5 seconds. While it is probably not yet a perfect...

This has now been merged here: https://github.com/cherrypy/cheroot/pull/401 Testing/verifying the idle CPU usage benefits would be welcome. On Windows systems, sadly a capped timeout needs to stay, as the connection handler...

Upgrade your CherryPy and cheroot to the latest version and check whether idle CPU usage on RPi 1 is now fine.

As of #378 and https://github.com/cherrypy/cherrypy/issues/1908, hopefully we can finish this. Indeed `select()` should immediately return as fast as a connection is ready and the timeout only have an effect on...

Not sure how to use `tox`, it always misses some config file... I ran https://github.com/cherrypy/cheroot/pull/352#issuecomment-757554330 now via `py -m pytest -k test_response_latency test_wsgi.py` on current Windows 10 21H1 and Python...

Maybe [this](https://bugs.python.org/issue29256) is related? Probably someone has an idea how to narrow it down to the naked selector's `select()` method, with a single socket, a single select() call without timeout,...

It makes sense that the load is reduced when the server threads are reduced, but also 10% idle load is much too high and limiting the threads has negative impact...