Re: JERI vs. JRMP performance penalties
"Cornelius, Martin (DWBI)" <[email protected]> Wed, 12 Dec 2007 09:56:01 -0700
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <531F9EE7AD1E874595D59997FD3EAEED03AA26D1@COSSMGMBX05.EMAIL.CORP.TLD> |
Hi Bob, you wrote: > FYI, you might try HttpServerEndpoint rather than TcpServerEndpoint, > you should find its performance closer to that of JRMP. Of course, it is ! With JERI/HttpServerEndpoint, the throughput is just about factor 2 lower than with JRMP. Hence, the multiplexing performed by TcpEndpoint indeed seems to be in duty for some of the performance differences. BTW, i just convinced myself that multiplexing not only is engaged if concurrent calls between 2 specific objects are processed (what i thought so far), but that remote method invocations from multiple clients on VM A to multiple servers on VM B are multiplexed onto one socket, if the servers are exported via the same exporter. This is a really usefull feature for us, as we are urged to use as little sockets as possible. > One trivial thing I noticed in trying your example, in the > JeriServerthere's no Thread.sleep and nothing's holding a strong ref > to the server, so a GC when the server happens to be idle can cause > it to exit. Many thanks for your advice, being a java newbie i still like to fail into traps left by GC'ed objects. Martin ************************************************ The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ************************************************ -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]