Yes, but it seems that is more of a workaround tha...

# ktor

[spand]

Yes, but it seems that is more of a workaround than an actual solution. Let me try again so we can down to the core of it.

Consider the following scenario:
A server, over the course of a minute, recieves requests for 10x capacity.
Jetty has after this minute placed tasks for each request in the ktor pool.
We process the work directly in the get("/") { processWork() }
The server will now be busy for 9 minutes processing work generated in that first minute.

If I have made a mistake in the above please correct me but assuming not: Do you consider this expected/wanted out of the box behaviour ?