Closed GoogleCodeExporter closed 9 years ago
Scala's specialized would be perfect here. I'm not sure if there is enough
value for this effort in Java-land, though.
To improve concurrency often relies on increasing the memory footprint. I
suspect that use cases that need the higher concurrency characteristics are
less memory sensitive. If memory was a concern, then a different language (e.g.
C) might be used.
Do you have a good example to justify this request or was this an observation?
Original comment by Ben.Manes@gmail.com
on 20 Apr 2011 at 2:43
It was just an observation, I use the trove collections for everything when I
don't need concurrency. If you compare the performance of the trove hashmaps
compared to the standard hashmap the performance and memory footprint are much
better by a long shot. I am sure that eliminating autoboxing/unboxing
contributed to the speedup and reduced memory footprint.
I would not put it high on your todo list but it would be a nice thing to have
at some point.
Original comment by pariodeu...@googlemail.com
on 20 Apr 2011 at 9:44
Due to being backed by ConcurrentHashMap, the effort required is considerable.
Unfortunately Java is not friendly to these types of optimizations and its too
much work for me to take on.
Original comment by Ben.Manes@gmail.com
on 20 Apr 2011 at 10:07
Original issue reported on code.google.com by
pariodeu...@googlemail.com
on 20 Apr 2011 at 1:40