Hi Mladen...I'd be also be interested in your thoughts about the main
aspect to my question concerning JBossWeb behaviour with APR in regards
to new connection establishment. Specifically, because on Win32 the
backlog queue is limited to 200, it's easy to get not very graceful DoS
behavior to a
Remy Maucherat wrote:
Why is poller performance bad in Windows? Is that a consequence of the
I've been told it uses select, which works only on 64 sockets at a time.
So if you have a large poller, then the poll call performance degrades.
Mladen is really the only one who can answer Windows qu
Why is poller performance bad in Windows? Is that a consequence of the
I've been told it uses select, which works only on 64 sockets at a time.
So if you have a large poller, then the poll call performance degrades.
Mladen is really the only one who can answer Windows questions.
(personal
On Wed, 2009-04-29 at 08:50 +1000, mcto...@gmail.com wrote:
> A few followups on this. It's only now that I have realised that the
> the tomcat apr handler in JBoss is subtly different from the one in
> Tomcatie that whole piece of tomcat has been forked into JBossWeb,
> and they're startin
A few followups on this. It's only now that I have realised that the
the tomcat apr handler in JBoss is subtly different from the one in
Tomcatie that whole piece of tomcat has been forked into JBossWeb,
and they're starting to diverge. Be that as it may, my comments cover
the current des
On Wed, 2009-04-29 at 00:42 +1000, mcto...@gmail.com wrote:
> In a nutshell, we discovered that under Windows, the maximum size of the
I think with Windows, APR will have scalability problems sooner or
later, as poller performance is bad on that platform (the code has a
hack to use many pollers a
