[ https://jira.jboss.org/jira/browse/JBMESSAGING-1680?page=com.atlassian.ji... ] Howard Gao commented on JBMESSAGING-1680: ----------------------------------------- I have measured the start-up time of three components of JBM: Server Peer, Messaging Office and GroupMember. The GroupMember is contained in the Messaging Office startup process. Using JBoss 4.2.3.GA, I tested the timing in three cases: single node non clustered with hsql, single node non clustered with mysql, and two nodes clustered with mysql. The result shows 1. The Messaging Office (and GroupMember in clustered case) takes much more longer time to start up in clustered case than in non-clustered case. In single non-clustered case, Messaging Office takes very little time (e.g. 5ms or 31ms) to start. But in clustered case, it takes more than 6 sec to start up, of which 98% to 99% are taken by GroupMember. Of the total startup time of GroupMember, around 98% are devoted to the connection of two jgroup channels. And between the two channels, the control channel takes about 30% of the time and the data channel takes about 65%. So if we can start the two channels concurrently, we may save some time. See the data: Total duration: 6107 [GroupMember] ----------------------------------------------- [create-control-channel] : dur 17 ---> 0.28% [create-data-channel] : dur 32 ---> 0.52% [connect-control-channel] : dur 2011 ---> 32.93% [connect-data-channel] : dur 4047 ---> 66.27% ----------------------------------------------- Total duration: 6220 [Messaging PostOffice] ----------------------------------------------- [super-start] : dur 15 ---> 0.24% [office-init] : dur 0 ---> 0.0% [get-bindings-from-storage] : dur 33 ---> 0.53% [groupmember-start] : dur 6118 ---> 98.36% [cluster-init] : dur 47 ---> 0.76% [load-bindings] : dur 7 ---> 0.11% ----------------------------------------------- 2. In all cases the ServerPeer start takes a relative short and constant time (around 100ms), see the data: a) Clustered case -- node0, it takes 99 ms Total duration: 99 [Server Peer] ----------------------------------------------- [load-aop-config] : dur 30 ---> 30.3% [members-creation] : dur 45 ---> 45.45% [start-id-mgrs] : dur 16 ---> 16.16% [start-jndi-mappers] : dur 1 ---> 1.01% [start-conn-mgrs] : dur 5 ---> 5.05% [start-msg-store] : dur 0 ---> 0.0% [start-tx-repo] : dur 0 ---> 0.0% [loading-tx-repo] : dur 2 ---> 2.02% [start-msg-counters] : dur 0 ---> 0.0% ----------------------------------------------- b) Non clustered case -- mysql, it takes 101 ms Total duration: 101 [Server Peer] ----------------------------------------------- [load-aop-config] : dur 32 ---> 31.68% [members-creation] : dur 43 ---> 42.57% [start-id-mgrs] : dur 23 ---> 22.77% [start-jndi-mappers] : dur 0 ---> 0.0% [start-conn-mgrs] : dur 2 ---> 1.98% [start-msg-store] : dur 0 ---> 0.0% [start-tx-repo] : dur 0 ---> 0.0% [loading-tx-repo] : dur 1 ---> 0.99% [start-msg-counters] : dur 0 ---> 0.0% ----------------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1680?page=com.atlassian.ji... ] Howard Gao closed JBMESSAGING-1680. ----------------------------------- Resolution: Done done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira