Skip to main content

Benchmarking high performance java collection framework

I am an ultimate fan of java high performance framework or library. Java native collection framework always works with primitive wrapper class such as Integer, Float e.t.c. Boxing and unboxing of wrapper class to primitive data type always decrease the java execution performance. Most of us, always looking for such a library or framework to works with primitive data type in collections for increasing performance of Java application. Most of the time i uses javolution framework to get better performance, however, this holiday i have read about a few new java collections frameworks and decided to do some homework benchmarking to find out, how much they could better than Java native collection framework.
I have examine two new java collection framework, one of them are fastutil and another one are HPPC. For benchmarking i have used java JMH with mode Throughput. For benchmarking i took similar collection for java ArrayList, HashSet and HasMap from two above described frameworks.
Collections:
  1. ArrayList
  2. HashSet
  3. HashMap
Datatype:
Integer for Java native collection and int for HPPC and fastutils.
Host machine configuration:
OS: OSX El Capitan
CPU: 4
RAM: 16
HDD: SDD
JMH Configuration:
Fork: 10
iteration: 10
warm iteration: 10
Benchmark of List:
  1. Java native: ArrayList<Integer>
  2. FastUtil:it.unimi.dsi.fastutil.ints.IntArrayList
  3. HPPC:com.carrotsearch.hppc.IntArrayList
Number of elements: 10 000
Operations: add, retrieve by Iterator
Result of the benchmark is as follows:
it's obvious that FastUtil IntArrayList collection win with huge score. if you are wonder and decided that fastutil framework will always win the benchmark, you will be surprised. Lets examine another collections
Benchmark of Set:
  1. Java native: HashSet<Integer>
  2. FastUtil:it.unimi.dsi.fastutil.ints.IntSet
  3. HPPC:com.carrotsearch.hppc.IntHashSet
Number of elements: 10 000
Operations: put, retrieve by Iterator
Result of the benchmark is as follows:
Wonder!! me too, i have over checked the code. Java native HashSet wins over all other framework, very interesting the result of the fastutil score, it's only 89.
Benchmark of Map:
  1. Java native: HashMap<Integer>
  2. FastUtil:it.unimi.dsi.fastutil.ints.Int2IntArrayMap
  3. HPPC:com.carrotsearch.hppc.IntIntHashMap
Number of elements: 10 000
Operations: put, retrieve by Iterator
Result of the benchmark is as follows:
Similar score with Set, Java native Map is wining over other frameworks. Question is, why fastutil collection framework giving such a poor score? Answer of this question we will examine in next few blogs.

Comments

Popular posts from this blog

Apache Ignite deep dive, SQL engine

Apache Ignite  is an open source memory-centric distributed database, caching and comput- ing platform. From the beginning, it was designed as an in-memory data grid for developing a high-performance software system. So, it’s core architecture design is slightly different from the traditional NoSQL databases, which can simplify building modern applications with a flexible data model and simpler high availability, high scalability.     Moreover, to understand how to design application with any databases or framework properly, you must understand the architecture of the database or framework itself. By getting a better idea of the system, you can solve different problems in your enterprise architecture landscape, can select a comprehensive database or framework that is appropriate for your application and get the maximum benefits from the system. In this article we are going to explore the Apache Ignite SQL engine.      Under the hood...

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title  The Apache Ignite book  has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...