Hey
marc fleury wrote:
> We are not interested in a vs benchmark :)
>
> however I will say this. We use the RMI native implementation for the
> invocations so it is t3 vs RMI.
>
> Rickard do you have input there?
Well, one of the features with T3 is that if a client does concurrent
calls to the JVM then it does multiplexing, whereas JRMP will use
multiple connections. Also, I think T3 has some JNI stuff to get around
the one thread/one connection limitation.
Of course, when JDK 1.4 comes out we will get this too, since that is
scheduled for inclusion in the JDK and JRMP.
I also wish to stress that this is only important if you have
application or applet clients. For web server clients, the number of
connections is restricted by the web servers thread pool size, and
irrelevant in the in-VM case (since no wire protocol at all is used
then).
I tested to put in a restriction on the number of concurrent threads
before (e.g. only 10 threads could do concurrent work), but didn't see
any improvements in performance. We might want to put that back in when
testing thousands of clients/threads and see if it has any impact (it
should).
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
