I noticed excessive CPU usage in HashMap lookups in StatsDAggregator.
The stacks shows that the HashMap had devolved into a TreeMap which
happens after frequent hash collisions. That got me looking at the
implementations of hashCode/equals in the Message heirarchy and
this seems a likely culprit.
I noticed excessive CPU usage in HashMap lookups in StatsDAggregator. The stacks shows that the HashMap had devolved into a TreeMap which happens after frequent hash collisions. That got me looking at the implementations of hashCode/equals in the Message heirarchy and this seems a likely culprit.