|
From: | silvioprog |
Subject: | Re: [libmicrohttpd] Problem with Keep-Alive and MHD_OPTION_CONNECTION_TIMEOUT in MHD_USE_THREAD_PER_CONNECTION mode |
Date: | Mon, 7 Dec 2015 18:29:09 -0300 |
[...]
Well, on Linux C10k is easy these days. We had people using MHD that in
practice had what you might call the C100k problem, and that was doable ;-).
Well, thread-per-connection was never the most scalable option,
especially if used like this...
If you really need to hit MHD with thousands of parallel requests, you
may want to consider using the thread *pool* (set the thread pool size).
Not necessarily. Using thread-per-connection will use way more RAM, but
fewer expensive system calls. So until you hit your memory limit or run
into scheduler problems, thread-per-connection can be more scalable,
especially on W32 where the current 'select()'-mechanism is rather
awkward AFAIK.
But even on GNU/Linux thread-per-connection can be faster as long as
your system can handle all the threads (and doesn't encounter trouble
with cache misses for all the stacks).
[Prev in Thread] | Current Thread | [Next in Thread] |