On Tue, Nov 24, 2015 at 7:00 AM, <dancer-users-request@dancer.pm> wrote:

This means that if you write your Dancer route handlers to be efficient, so that they return within a few milliseconds at most, you can in effect serve a great many clients, since most of them will be idle most of the time.

The single-threaded web server only breaks down when you start getting to load levels where the server is handling at least one connection all the time, so that allowing to to handle a second or third in parallel can provide some benefit.

What if your route handler goes to disk for something (perhaps a DB access)? Your other Starman process(es) could start handling another connection in the meantime. What if your CPU has 2 or more cores (likely)? Again, the other process could get going.

Maybe you have low traffic on an Intranet. But out on the Internet, you could have bots and spiders bothering your route handlers just when you have a real client to serve.

Cheers -- Rick