[ http://jira.jboss.com/jira/browse/JGRP-394?page=all ] Bela Ban updated JGRP-394: -------------------------- Description: - NAKACK.handleMessage(): NakReceiver.add() --> Retransmitter.add() --> TimeScheduler.add() is quite costly; we also iterate through a linear list when removing a message from the Retransmitter ! - Bundler: sending is over-synchronized was: - NAKACK.handleMessage(): NakReceiver.add() --> Retransmitter.add() --> TimeScheduler.add() is quite costly; we also iterate through a linear list when removing a message from the Retransmitter ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-394?page=all ] Bela Ban updated JGRP-394: -------------------------- Description: - NAKACK.handleMessage(): NakReceiver.add() --> Retransmitter.add() --> TimeScheduler.add() is quite costly; we also iterate through a linear list when removing a message from the Retransmitter ! - Bundler: sending is over-synchronized; use ConcurrentHashMap for msgs - GroupRequest and RequestCorrelator eat CPU cycles in MessageDispatcher: remove them ? was: - NAKACK.handleMessage(): NakReceiver.add() --> Retransmitter.add() --> TimeScheduler.add() is quite costly; we also iterate through a linear list when removing a message from the Retransmitter ! - Bundler: sending is over-synchronized; use ConcurrentHashMap for msgs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-394?page=all ] Bela Ban updated JGRP-394: -------------------------- Fix Version/s: 2.6 (was: 2.5) Affects Version/s: 2.5 (was: 2.4) moved to 2.6, as this is a performance optimization -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-394?page=all ] Bela Ban resolved JGRP-394. --------------------------- Resolution: Done Looked at Bundler: we don't need a ConcurrentHashMap as access to msgs is very short and we need to synchronize anyway -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira