Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1851
@wy96f Np you can pick up the master and push a new PR with the new changes
that are more improvements/gardening than fixes.
IMO would be interesting to:
- drop the (completly useless) benchmark on ConcurrentLongHashMapTest
- investigate re lazySet on capacity (probably just an Unsafe::storeFence
would enough)
- investigate re lazySet on size or just making it a plain field and do
something like:
```
public int size() {
int size = 0;
for (Section<V> s : sections) {
//read acquire the lock state and any written size
s.tryOptimisticRead();
size += s.size;
}
return size;
}
```
- [advanced] investigate about padding to avoid false sharing between
Section fields
---
