Fastest way to lock/synchronize objects.

Overview


There have been some comparison of Lock vs synchronization in Java. I wanted to compare the latest version of Java with using a plain AtomicLong and AtomicReference as an alternative to locking.


Summary

The results are much the same for Java 5.0 and later, provided your JIT has optimised the code. I found this required the methods to be called between 10K and 50K times to get the best optmisation (depending on the approach used)

In short, the fastest way to perform lock/synchronization is to make sure your JVM is warmed up first.


Results

The tests were single threaded and run on a 3 GHz Xeon processor running SLES 11.

Timings are in nano-seconds, that is one billionth of a second. For Java 1.4.2 I used the backport v2.1

Versionbits concurrent Lock synchronized AtomicLong AtomicReference
1.4.2 u 18 32 130 40 115 105
5.0 u 22 64 23 15 15 16
6 u 764 21 20 14 15
6 u 20 32 23 20 19 12
6 u 20 64 16 20 12 13
7 eap b76 32 23 20 19 12

Comments

  1. pveentjer19 June 2010 at 15:43

    Afaik a intrinsic lock (so a synchronized statement or method) has support for biased locking, making acquiring a lock the second time by the same thread much cheaper.

    I don't know at which releases it is enabled or disabled, but testing using a single thread really could give unexpected results.

    ReplyDelete
  2. Peter Lawrey19 June 2010 at 17:37

    This is true, I would be interested in what anyone else has found. I intend to run the same test with multiple threads.

    ReplyDelete
  3. RPidugu1 July 2010 at 07:29

    Hi..Thanx for your suggestion on my blog: http://javaj2eeplanet.blogspot.com

    -ReDs
    http://funkyxone.blogspot.com

    ReplyDelete

Post a Comment

Popular posts from this blog

Java is Very Fast, If You Don’t Create Many Objects

Image
  You still have to watch how many objects you create. This article looks at a benchmark passing events over TCP/IP at 4 billion events per minute using the net.openhft.chronicle.wire.channel package in Chronicle Wire and why we still avoid object allocations..  One of the key optimisations is creating almost no garbage. Allocation is a very cheap operation and collection of very short-lived objects is also very cheap. Does this really make a difference? What difference does one small object per event (44 bytes) make to the performance in a throughput test where GC pauses are amortised? While allocation is as efficient as possible, it doesn’t avoid the memory pressure on the L1/L2 caches of your CPUs and when many cores are busy, they are contending for memory in the shared L3 cache.  Results Benchmark on a Ryzen 5950X with Ubuntu 22.10. JVM Vendor, Version No objects Throughput, Average Latency* One object per event Throughput, Average Latency* Azul Zulu 1.8.0_322 60.6 ...
Read more

System wide unique nanosecond timestamps

A Unique Identifier can be very useful for tracing. Those ids are even more useful when they contain a high-resolution timestamp.  Not only do they record the time of an event, but if unique can help trace events as they pass through the system. Such unique timestamps however can be expensive depending on how they are implemented.   This post explores a lightweight means of producing a unique, monotonically increasing system-wide nano-second resolution timestamp available in our open-source library. Uses for Unique Identifiers Unique identifiers can be useful to associate with a piece of information so that information can be referred to later unambiguously. This could be an event, a request, an order id, or a customer id. They can naturally be used as a primary key in a database or key/value store to retrieve that information later. One of the challenges of generating these identifiers is avoiding creating duplicates while not having an increasing cost.  You could ...
Read more

What does Chronicle Software do?

Image
Overview Chronicle Software is about simplifying fast data.  It is a suite of libraries to make it easier to write, monitor and tune data processing systems where performance and scalability are concerned. But its free, how do you make money, through support? We offer premium support . However, we often hear from users for the first time about a year after they have it in production.  Most users find they can support the software themselves.  It is only after a year or so, they have questions or concerns about where to take the product next.  In many cases, it is to a problem we have already solved and they just need to upgrade their software or use a new module we have added. As we don't know who is using most of our software, we can't advise them on how best to use our software and what updates or enhancements they would benefit from. We need users to contact us and ask questions.  We have a free forum , and we respond to 50% of questions in 2 hours...
Read more