We are using the KISS principle to do the design. In the earlier version we just focus on implement the function and then we keep polish the code by using refactor techs. So if you have some good idea, you can present it in the mailing list and do some POC for it. We don't have other reason to reject the proposal if it fix the performance issue.
Using the PriorityBlockingQueue could be a good choice for the fasterSender, but we still need to build a pool for the connected message sender. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Aug 4, 2018 at 12:24 AM, 黎 先生 <[email protected]> wrote: > The method iterates over all entry set everytime. This might cause a > performance problem. > > Why not considering java.util.concurrent.PriorityBlockingQueue instead ? > Or design a sorted data structure for the MessageSenders. > > Is there any other considerations? > > > >
