poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 61722] Review ways to avoid new Integer()/Integer.valueOf() in performance sensitive places
Date Fri, 03 Nov 2017 23:32:18 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=61722

--- Comment #1 from Greg Woolsey <gwoolsey@apache.org> ---
This article[1] has an interesting set of tests, results, and summary info for
multiple primitive collections frameworks, including Trove.

Most interesting points to me:
 * Trove isn't under active development, and hasn't been for a few years.  It
was also slowest.
 * Fastutil is the overall winner for performance, although memory wasn't a
consideration in these tests.
 * Fastutil is a 28M JAR file (!)

If we are only interested in Map<int, ? extends Object> type maps, perhaps a
slimmed-down version of a stable build of Fastutil could be used.  It appears
license compatible, and we could investigate an AutoJar or similar step added
to the build to create an artifact bundled/released with POI.

[1]
http://java-performance.info/hashmap-overview-jdk-fastutil-goldman-sachs-hppc-koloboke-trove-january-2015/

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Mime
View raw message