How well can JDK's LocateRegistry do in performance?

[lightning]

I've no idea of this server's performance, does somebody has
experience about that to share?

 

[EJP]

I've no idea of this server's performance, does somebody has
experience about that to share?

(a) java.rmi.registry.LocateRegistry is not a server.

(b) If you're asking about the performance of
java.rmi.registry.LocateRegistry.getRegistry() over the network, it
doesn't do anything over the network. It just constructs a local
Registry stub that refers to the hostort you specify. Only when you
*use* that stub will anything happen over the network.

(c) If you're asking something else, you need to clarify.

 

[lightning]

I ask about LocateRegistry.createRegistry(),it start a daemon thread
and lauched a server.

 

[EJP]

I ask about LocateRegistry.createRegistry(),it start a daemon thread
and lauched a server.

So none of that should take very long. What aspect of 'performance' are
you interested in?

 

[lightning]

So none of that should take very long. What aspect of 'performance' are
you interested in?

Thanks for your attention, the performance,for example: how many
requests it can handle and process correctly per second?

 

[EJP]

Thanks for your attention, the performance,for example: how many
requests it can handle and process correctly per second?

Same as any other RMI server. That's all it is. But I don't understand
why this would be a concern. The Registry isn't a bottleneck. You look
it up *once* in the lifetime of each client. Calls per second don't come
into it. Calls per day might.

 

[lightning]

Same as any other RMI server. That's all it is. But I don't understand
why this would be a concern. The Registry isn't a bottleneck. You look
it up *once* in the lifetime of each client. Calls per second don't come
into it. Calls per day might.

So we should keep the stubs storing in a singleton object and just
look up for them lazily, that's the best practice,right?

 

[EJP]

So we should keep the stubs storing in a singleton object and just
look up for them lazily, that's the best practice,right?

Exactly, or when you get NoSuchObjectException.