Sponge: Use FastUtil rather than Trove for more memory efficient collections and maps.

Created on 13 Mar 2016 · 5Comments · Source: SpongePowered/Sponge

Whilst Trove has been around for a while, it isn't as actively developed anymore. FastUtil is much more recent, and actively developed.

On top of this, Trove doesn't hold up in terms of performance compared to more modern libraries. Here's an example of a benchmark that pits numerous libraries together,

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

Another option is Koloboke, which appears to include enhanced integration with JDK8.

low input wanted

Source

me4502

👍2

Most helpful comment

Now that Minecraft is including a subset of fastutil it makes sense to use that in place of trove.

amaranth on 14 Apr 2016

👍3

All 5 comments

Koloboke is looking to be a better option, as the FastUtil jar is 17mb.

me4502 on 13 Mar 2016

@amaranth

Your thoughts on this?

Zidane on 13 Mar 2016

Koloboke's full JAR is even bigger (about 18 MB), so if we'd choose one of them we'd need to filter the unused classes out before shading, because that would be otherwise way to big to shade completely.