- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: 2002. január 8. 16:35
Subject: Re: nbio connector
, and could
use a helping hand here and there. In fact, I already have much of
the code for building
In few days we'll have the jk2 working, so you can play with
unix domain
sockets - that should improve a bit the performance. There are few
other optimizations there ( more agressive recycling, etc ) - and
we really need help testing it and feedback.
( I have it working on my machine, but I'm
On Fri, 11 Jan 2002, GOMEZ Henri wrote:
Unix domain will be faster on systems running Apache and Tomcat on
the same box, so faster network IO will still be fine for configuration
with separate Webserver and Tomcat (security concerns or load-balancing)
Of course, different issues. For 'lb'
I believe someone on this list once said something like open
source development: have fun or get paid for it. I'm working
on NIO solely because it's a fun new technology in Java with a
huge potential, and if it happens to turn out useful it's a
clear win. :-)
NBIO is really an interesting
.
Attila.
- Original Message -
From: Daniel Rall [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: 2002. január 10. 0:26
Subject: Re: nbio connector
Have you looked at Matt Welsh's SEDA
http://www.cs.berkeley.edu/~mdw/proj/sandstorm
El Jueves 10 Enero 2002 06:16, GOMEZ Henri escribió:
I believe someone on this list once said something like open
source development: have fun or get paid for it. I'm working
on NIO solely because it's a fun new technology in Java with a
huge potential, and if it happens to turn out useful
On Thu, 10 Jan 2002, Mauricio Nuñez wrote:
Keep on this works, since the benchs I saw on Matt site
were more than interesting on heavily servers.
I will try to get NBIO work as a Ajp13 connector, because my site it's very
high loaded ( IMHO ), and i NEED to get a better performance.
In
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: 2002. január 8. 17:35
Subject: Re: nbio connector
I'm a bit sceptical about the usefulness of the thing, then, since reading
and parsing requests headers is by far
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: 2002. január 8. 19:19
Subject: Re: nbio connector
I agree on both the points above.
Especially the first one actually, since you can avoid wasting a thread on
waiting
- Original Message -
From: [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: 2002. január 8. 20:35
Subject: Re: nbio connector
I'm not very sure about nbio - most of the time there's a lot
of complexity ( and a different programming model, etc
El Miércoles 09 Enero 2002 06:52, Attila Szegedi escribió:
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: 2002. január 8. 17:35
Subject: Re: nbio connector
I'm a bit sceptical about the usefulness of the thing
Attila Szegedi wrote:
(as it stands now in JDK 1.4, a single thread can manage up to 63
channels so you still need multiple threads, only less than with
blocking approach),
The 63 channel limit is a Windows-only bug in the Beta,
designing code around it probably isn't a good idea.
--
Well I didn't want to bring this to the sunlight so soon but since you brought up the
issue:
I'm developing a generic non-blocking server framework for JDK 1.4.
It handles all subtleties of the non-blocking server's life, such as non-blocking
pipes for servlet output buffering, thread scaling
My primary goal for bringing the code in the public is that I want
to build a HTTP/1.1 connector for Tomcat 4.0 based on it
I don't think you can have a nbio connector with a compliant servlet
container, because the J2EE spec mandates at the moment: 1 thread - 1
request.
That requirements
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: 2002. január 8. 16:35
Subject: Re: nbio connector
My primary goal for bringing the code in the public is that I want
to build a HTTP/1.1 connector for Tomcat 4.0 based
I don't think I conflict with this requirement. In fact,
to execute a servlet's service() method still requires
a separate thread. In my design, the connector first reads
the request line and the headers in a non-blocking fashion,
naturally multiplexing up to 63 requests on a single thread.
Remy Maucherat wrote:
With my design, you still need one thread/request but only for the
time required to process container.invoke()
In the real world, the servlets and JSPs are the thing which take by far the
most time to complete, so I'm not sure you wouldn't end up spending a lot of
Developers List [EMAIL PROTECTED]
Sent: Tuesday, January 08, 2002 8:35 AM
Subject: Re: nbio connector
| I don't think I conflict with this requirement. In fact,
| to execute a servlet's service() method still requires
| a separate thread. In my design, the connector first reads
| the request line
Remy Maucherat wrote:
With my design, you still need one thread/request but only for the
time required to process container.invoke()
In the real world, the servlets and JSPs are the thing which take by far
the
most time to complete, so I'm not sure you wouldn't end up spending a
My opinion on the nbio issue:
I completely agree with Remy, the IO is not the issue at least
for the current code and the near future. The char-byte
conversions are far more expensive.
JDK1.4 provides a very nice solution for the char conversions,
however my tests show it to be comparable in
[EMAIL PROTECTED] wrote:
I'm not very sure about nbio - most of the time there's a lot
of complexity ( and a different programming model, etc )
Yes.
- and the benefits seems pretty small.
It depends. Using NIO, you can serve static content as fast
or faster than Apache 1.3 in pure
21 matches
Mail list logo
