|
> 2. Does dolphin do anything to spawn new threads/processes when requests
> come in? (I think Apache does this).
Dolphin does nothing when a new request comes in, infact, it doesn't even
handle requests. You would have to write a server for that, in which case,
you would probably implement what you are after.
I believe Swazoo spawns a new process per http request.
> 3. Is some of this out of the auspices of Dolphin...maybe in the winsock
> implementation?
The Dolphin sockets are built on top of Winsock, so yeah, any limitation
that applies to winsock, would also apply to Dolphin.
> 4. which of: spray, swazoo, fs fastcgi are more recommended for this level
> of transaction rate? Is there something else?
You would have to test it yourself. I mean, it depends on what you are
doing. I can get FastCGI to handle 220 requests per second, but as soon as I
actually have it do anything, the requests per seconds drops quit
significantly.
I would imagine the overhead of Spray soap envelopes would kill your
performance right off.
> If Dolphin is unsuitable for this application, I'm not sure what i'll go
> with...possibly a C++ front end.
Sure, you could write it in C++... Do you chew glass for fun too?
:)
|