Which concurrent Queue implementation should I use in Java?

by

ConcurrentLinkedQueue means no locks are taken (i.e. no synchronized(this) or Lock.lock calls). It will use a CAS – Compare and Swap operation during modifications to see if the head/tail node is still the same as when it started. If so, the operation succeeds. If the head/tail node is different, it will spin around and try again.

LinkedBlockingQueue will take a lock before any modification. So your offer calls would block until they get the lock. You can use the offer overload that takes a TimeUnit to say you are only willing to wait X amount of time before abandoning the add (usually good for message type queues where the message is stale after X number of milliseconds).

Fairness means that the Lock implementation will keep the threads ordered. Meaning if Thread A enters and then Thread B enters, Thread A will get the lock first. With no fairness, it is undefined really what happens. It will most likely be the next thread that gets scheduled.

As for which one to use, it depends. I tend to use ConcurrentLinkedQueue because the time it takes my producers to get work to put onto the queue is diverse. I don’t have a lot of producers producing at the exact same moment. But the consumer side is more complicated because poll won’t go into a nice sleep state. You have to handle that yourself.

More Related Contents:

  1. LinkedBlockingQueue vs ConcurrentLinkedQueue
  2. What’s the difference between Thread start() and Runnable run()
  3. Why must wait() always be in synchronized block
  4. ExecutorService that interrupts tasks after a timeout
  5. Producer/Consumer threads using a Queue
  6. Volatile vs Static in Java
  7. When would you call java’s thread.run() instead of thread.start()?
  8. What are the main uses of yield(), and how does it differ from join() and interrupt()?
  9. What are the advantages of using an ExecutorService?
  10. What’s a monitor in Java?
  11. Java threads and number of cores
  12. Impossible to make a cached thread pool with a size limit?
  13. When should I use a CompletionService over an ExecutorService?
  14. Are non-synchronised static methods thread safe if they don’t modify static class variables?
  15. Forcing multiple threads to use multiple CPUs when they are available
  16. Simplest and understandable example of volatile keyword in Java
  17. ThreadPoolExecutor Block When Queue Is Full?
  18. Java ExecutorService: awaitTermination of all recursively created tasks
  19. Why does Java not see the updated value from another thread?
  20. Why does java.util.concurrent.ArrayBlockingQueue use ‘while’ loops instead of ‘if’ around calls to await()?
  21. What is adaptive spinning w.r.t lock acquisition?
  22. Why should I use concurrent characteristic in parallel stream with collect?
  23. Jboss Java EE container and an ExecutorService
  24. Why doesn’t volatile in java 5+ ensure visibility from another thread?
  25. Thread Confinement
  26. How can I wrap a method so that I can kill its execution if it exceeds a specified timeout?
  27. How to pause/resume all threads in an ExecutorService in Java?
  28. Java, divide incoming work uniformly via hashing in multithreaded evnironments
  29. notifyAll() throws IllegalMonitorStateException
  30. Will a chain of method calls (CompletableFuture API) execute asynchronously if the first method in a chain is asynchronous?

Leave a Comment