liyangbing commented on issue #249: master-slave sync model performance improve URL: https://github.com/apache/rocketmq/issues/249#issuecomment-389417176 i understand the question, i have two question first question handleDiskFlush(result, putMessageResult, msg); handleHA(result, putMessageResult, msg); if i change the order of two statement, master slave flush disk parallelly， will we improve performance further? handleHA(result, putMessageResult, msg); handleDiskFlush(result, putMessageResult, msg); second question with the improve of performance, we will have more processing threads the last statement of "lock synchronize" will spend more time we use 3.2.6 version have 300+ applications, the following warning exceed 20+ everyday 2018-05-16 13:36:23 WARN SendMessageThread_101 - putMessage in lock eclipse time(ms) 1382 2018-05-16 12:22:05 WARN SendMessageThread_2 - putMessage in lock eclipse time(ms) 1111 2018-05-16 12:16:34 WARN SendMessageThread_138 - putMessage in lock eclipse time(ms) 1060 2018-05-16 11:24:16 WARN SendMessageThread_60 - putMessage in lock eclipse time(ms) 1154 2018-05-16 10:02:34 WARN SendMessageThread_62 - putMessage in lock eclipse time(ms) 1310 2018-05-16 09:21:15 WARN SendMessageThread_12 - putMessage in lock eclipse time(ms) 1573 2018-05-16 09:11:35 WARN SendMessageThread_94 - putMessage in lock eclipse time(ms) 1046 2018-05-16 04:38:34 WARN SendMessageThread_70 - putMessage in lock eclipse time(ms) 1327 2018-05-16 04:08:01 WARN SendMessageThread_67 - putMessage in lock eclipse time(ms) 1084 2018-05-16 03:57:03 WARN SendMessageThread_134 - putMessage in lock eclipse time(ms) 1074 2018-05-16 03:11:35 WARN SendMessageThread_139 - putMessage in lock eclipse time(ms) 1882 the following warning exceed 500+ everyday 2018-05-16 14:51:19 WARN SendMessageThread_73 - putMessage not in lock eclipse time(ms) 1015 2018-05-16 14:51:19 WARN SendMessageThread_2 - putMessage not in lock eclipse time(ms) 1015 2018-05-16 14:51:19 WARN SendMessageThread_132 - putMessage not in lock eclipse time(ms) 1015 2018-05-16 14:51:19 WARN SendMessageThread_41 - putMessage not in lock eclipse time(ms) 1190 2018-05-16 14:51:19 WARN SendMessageThread_131 - putMessage not in lock eclipse time(ms) 1011 2018-05-16 14:51:19 WARN SendMessageThread_11 - putMessage not in lock eclipse time(ms) 1015 2018-05-16 14:51:19 WARN SendMessageThread_124 - putMessage not in lock eclipse time(ms) 1011 2018-05-16 14:51:19 WARN SendMessageThread_8 - putMessage not in lock eclipse time(ms) 1015 2018-05-16 14:51:19 WARN SendMessageThread_113 - putMessage not in lock eclipse time(ms) 1015 2018-05-16 14:51:19 WARN SendMessageThread_28 - putMessage not in lock eclipse time(ms) 1016 2018-05-16 14:51:19 WARN SendMessageThread_63 - putMessage not in lock eclipse time(ms) 1215 2018-05-16 14:51:19 WARN SendMessageThread_99 - putMessage not in lock eclipse time(ms) 1218 2018-05-16 14:51:19 WARN SendMessageThread_74 - putMessage not in lock eclipse time(ms) 1219 2018-05-16 14:51:19 WARN SendMessageThread_89 - putMessage not in lock eclipse time(ms) 1220 2018-05-16 14:51:19 WARN SendMessageThread_32 - putMessage not in lock eclipse time(ms) 1221
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
