Brian, Your right of course, I'm getting fast performance locally but I'm guilty of double buffering the data in the same network rpc call (and then some).
I could omit the data field and only pass it in the key but that would be too coarse grained (the entire value would be passed in the fqn as you mentioned below). One idea that I had before was to speed up the set search by doing a hashed search. I would need to have a consistent hashcode across the cluster for the same search value. Once, I find the matching bucket, compare the entries to see if they match the value. I have another idea as well that I'm going to try next. I'll write about it later. Thanks, Scott View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921628#3921628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921628 ------------------------------------------------------- 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
