News for hackers. Stuff that matters.

A comment on Native C/C++ Like Performance For Java Object Serialisation.

Re:Native C/C++ Like Performance For Java Object Serialisation by pron on Thursday July 05, 2012 @05:48PM (#4205155)
Network i/o puts a much bigger constraint on latency and throughput than serialization, so in practically all cases serializing to ByteBuffers using the standard ByteBuffer API (without resorting to Unsafe) would be just fine.
[ Parent | on HN ]
Re:Native C/C++ Like Performance For Java Object Serialisation by mjpt777 on Thursday July 05, 2012 @05:53PM (#4205182)
State of the art network hop is less than 3us so this is relevant. For on box IPC which can be as low as 100ns then very very relevant.
[ Parent | on HN ]
Re:Native C/C++ Like Performance For Java Object Serialisation by shrughes on Thursday July 05, 2012 @10:28PM (#4206086)
CPU can easily be the throughput bottleneck if you add enough network bandwidth.

It doesn't just happen in Java, it happens in C++ stuff too, and it can even be the throughput bottleneck for data going from the right kind of disk to the network -- that's why zero-copy I/O exists.

[ Parent | on HN ]