Java Benchmarks

System Environment

• Operation System：4.9.151-015.x86_64
• CPU：Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
• Byte Order：Little Endian
• L1d cache： 32K
• L1i cache：32K
• L2 cache： 1024K
• L3 cache： 33792K

JMH params

Don‘t skip warm up, otherwise the results aren’t accurate.

 -f 1 -wi 3 -i 3 -t 1 -w 2s -r 2s -rf cs

Benchmark Data:

Struct

Struct is a class with 100 primitive fields:

public class Struct {
  public int f1;
  public long f2;
  public float f3;
  public double f4;
  // ...
  public double f99;
}

Struct2

Struct2 is a class with 100 boxed fields:

public class Struct {
  public Integer f1;
  public Long f2;
  public Float f3;
  public Double f4;
  // ...
  public Double f99;
}

MediaContent

MEDIA_CONTENT is a class from jvm-serializers.

Sample

SAMPLE is a class from kryo benchmark

Benchmark Plots

Serialize to heap buffer

Serialize data java byte array.

Java schema consistent serialization

The deserialization peer must have same class definition with the serialization peer. No class forward/backward compatibility are supported in this mode.

Java schema compatible serialization

The deserialization peer can have different class definition with the serialization peer. Class forward/backward compatibility are supported in this mode.

Java schema consistent deserialization

The deserialization peer must have same class definition with the serialization peer. No class forward/backward compatibility are supported in this mode.

Java schema compatible deserialization

The deserialization peer can have different class definition with the serialization peer. Class forward/backward compatibility are supported in this mode.

Off-heap serialization

Serialize data off-heap memory.

Java schema consistent serialization

The deserialization peer must have same class definition with the serialization peer. No class forward/backward compatibility are supported in this mode.

Java schema compatible serialization

The deserialization peer can have different class definition with the serialization peer. Class forward/backward compatibility are supported in this mode.

Java schema consistent deserialization

The deserialization peer must have same class definition with the serialization peer. No class forward/backward compatibility are supported in this mode.

Java schema compatible deserialization

The deserialization peer can have different class definition with the serialization peer. Class forward/backward compatibility are supported in this mode.

Zero-copy serialization

Note that zero-copy serialization just avoid the copy in serialization, if you send data to other machine, there may be copies.

But if you serialize data between processes on same node and use shared-memory, if the data are in off-heap before serialization, then other processes can read this buffer without any copies.

Java zero-copy serialize to heap buffer

Java zero-copy serialize to direct buffer

Benchmark Data

Java Serialization

Java Zero-copy