Re: JERI vs. JRMP performance penalties

One trivial thing I noticed in trying your example, in the JeriServer
there'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.

At least on Solaris 10 with JDK 1.5 and 1.6, I've discovered that the
JERI client (but not the server) with NIO enabled is apparently causing
continous growth in non-heap (direct buffer) memory, and it gets to
a point where the client wedges for very long periods of time, not
eating up CPU time, not GCing, but somehow a fair bit of disk activity.
If/how soon this happens seems to depend on how heap size and
direct memory size are configured.  Not at all sure what the root
cause is at this point.

- Bob

--------------------------------------------------------------------------
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]