It looks like there is already a map maintained that we could try to use. Although, it maps Key to Object, I could probably use it to speed up the iterator. Our current iterator is getting the set of of keys and does a lookup on every call to Next.
I think that the lookup is hashed and should be fast, however, it might be faster to have our iterator get the set of all values in the map instead. I'll try this and see what kind of values I get out of it. Regarding your idea last night, I like it. I'm thinking that we might consider solving this at the JBoss (Tree) Cache level where we already deal with keeping things up to date across the cluster. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921694#3921694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921694 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
