Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1263
It makes sense for me!! I've to check the code for the addAll and about the
connections..there is another JIRA to be issued there: about using as
NettyConnectionI.getID() the hashCode of the Netty channel instead of
Channel::id(). But for different reasons: if 2 channels shares the same
hashcode (with big scale connections it could happen) you risk to pick the
wrong one in the map because they are sharing the same key!!!!
Changing subject! Very pleased by the results....I was expecting to be
good, but is even better, well done!
@clebertsuconic @michaelandrepearce Now IMHO it makes sense to reason if
the max growth size of a primitive ConcurrentMap after different resizing ops
is not too big to be retained in periods with low load...wdyt?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
