jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Herman <MHer...@NBME.org>
Subject Re: RMI for performance critical app
Date Fri, 13 Apr 2012 17:12:41 GMT

ajgoel wrote
> The documentation talks about RMI not being optimum for performance
> critical app. Can someone involved with this project please confirm if
> this statement (Note also that RMI remoting layer has not been optimized
> for performance) only applies to the standalone deployment
> http://jackrabbit.apache.org/standalone-server.html?

It doesn't matter how you deploy your jackrabbit, if you connect via RMI,
there isn't much that jackrabbit can do about the performance hit.

RMI as a technology is known for having bad performance regardless of
whatever code is on the other end.  It's convenient for just making
something work, but if your application has aggressive performance
requirements, running your code inside the same jvm as jackrabbit is the way
to go. The statement is simply saying that they've satisfied the "just work"
part of rmi (for the most part), but haven't gone in and tried to design
around the inherited limitations of the RMI protocol. 

View this message in context: http://jackrabbit.510166.n4.nabble.com/RMI-for-performance-critical-app-tp4555016p4555445.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message