You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Patricia Shanahan (JIRA)" <ji...@apache.org> on 2010/08/29 21:11:53 UTC

[jira] Created: (RIVER-347) Possible scaling issue in net.jini.lookup.ServiceDiscoveryManager findReg

Possible scaling issue in net.jini.lookup.ServiceDiscoveryManager findReg
-------------------------------------------------------------------------

                 Key: RIVER-347
                 URL: https://issues.apache.org/jira/browse/RIVER-347
             Project: River
          Issue Type: Improvement
          Components: com_sun_jini_lookup
         Environment: ServiceDiscoveryManager that communicates with a large number of lookup services.
            Reporter: Patricia Shanahan
            Priority: Minor


SDM stores a ProxyReg object wrapping the PortableServiceRegister for each known lookup. The ProxyReg has a reference to the PortableServiceRegister, but there is no quick mapping in the opposite direction. The method findReg obtains the ProxyReg for a given PortableServiceRegister by linear scan of an ArrayList containing a reference to each ProxyReg.

This is very efficient for a small number of lookup services, because the ArrayList scan has low overhead. It is inefficient for a large number of lookup services, especially if proxy discarding is frequent.

If a fix is needed, keep a HashMap<PortableServiceRegister,ProxyReg> representing the reverse mapping.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.