It looks like trove is not that fast as modern jdk collections with boxing and unboxing. tried multiple times on my home pc with add/remove/lookup operations, trove 2 times slower. is something wrong with my test environment? used LongObjectHashMaps with lots of elements.
--
You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mechanical-symp...@googlegroups.com.
Hello!
I’ve developed a Java parallel collections library (PJC) that improves the performance of the Java Collections. At this moment, thery are only implemented ArrayList and HashMap, and HashSet is being implemented.
You can download the source code and the benchmarks to probe Java, PJC, Trove and GoldmanSachs Collections here: https://forxa.mancomun.org/frs/?group_id=381
The documentation (at this moment, only in Spanish, but the graphics are easily understood) is available here: https://forxa.mancomun.org/docman/?group_id=381 . There, you can see the results of the execution of the benchmarks.
The project has also been uploaded to GitHub: https://github.com/mariaacha/PJC
If someone has any question, doubt or suggestion, can contact with me by email: PJa...@gmail.com
--
You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mechanical-symp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.