All Versions
51
Latest Version
Avg Release Cycle
136 days
Latest Release
-

Changelog History
Page 4

  • v2.10.1 Changes

    • 🐛 Bug fix, correct OSGI metadata.
    • ✂ Remove unnecessary code in wait strategies.

  • v2.10 Changes

    • ✂ Remove deprecated timeout methods.
    • ➕ Added OSGI metadata to jar file.
    • ✂ Removed PaddedAtomicLong and use Sequence in all places.
    • 🛠 Fix various generics warnings.
    • 🐎 Change Sequence implementation to work around IBM JDK bug and improve performance by ~10%.
    • ➕ Add a remainingCapacity() call to the Sequencer class.

  • v2.9 Changes

    • 🗄 Deprecate timeout methods for publishing.
    • ➕ Add tryNext and tryPublishEvent for events that shouldn't block during delivery.
    • 🐎 Small performance enhancement for MultithreadClaimStrategy.

  • v2.8 Changes

    • Create new MultithreadClaimStrategy that works between when threads are highly contended. Previous implementation is now called MultithreadLowContentionClaimStrategy
    • 🛠 Fix for bug where EventProcessors weren't being added as gating sequences to the ring buffer.
    • 🛠 Fix range tracking bug in Histogram

  • v2.7.1 Changes

    • 👀 Artefacts made available via maven central repository. (groupId:com.googlecode.disruptor, artifactId:disruptor) See UsingDisruptorInYourProject for details.

  • v2.7 Changes

    • 🔄 Changed construction API to allow user supplied claim and wait strategies
    • ➕ Added AggregateEventHandler to support multiple EventHandlers from a single BatchEventProcessor
    • 👌 Support exception handling from LifecycleAware
    • ➕ Added timeout API calls for claiming a sequence when publishing
    • 🚤 Use LockSupport.parkNanos() instead of Thread.sleep() to reduce latency
    • 🐎 Reworked performance tests to better support profiling and use LinkedBlockingQueue for comparison because it performs better on the latest processors
    • 🛠 Minor bugfixes

  • v2.6 Changes

    • 👷 Introduced WorkerPool to allow the one time consumption of events by a worker in a pool of EventProcessors.
    • 🆕 New internal implementation of SequenceGroup which is lock free at all times and garbage free for get and set operations.
    • SequenceBarrier now checks alert status on every call whether it is blocking or not.
    • ➕ Added scripts in preparation for publishing binaries to maven repository.

  • v2.5.1 Changes

    • 🛠 Bugfix for supporting SequenceReportingEventHandler from DSL. (issue 9)
    • 🛠 Bugfix for multi-threaded publishing to multiple ring buffers (issue 10)
    • 🔄 Change SequenceBarrier to always check alert status before entering waitFor cycle. Previously this was only checked when the requested sequence was not available.
    • 🔄 Change ClaimStrategy to not spin when the buffer has no available capacity, instead go straight to yielding to allow event processors to catch up.

  • v2.5 Changes

    • 🔄 Changed RingBuffer and publisher API so any mutable object can be placed in the RingBuffer without having to extend AbstractEvent
    • ➕ Added EventPublisher implementation to allow the publishing steps to be combined into one action
    • 👍 DisruptorWizard has been renamed to Disruptor with added support for any subtype of EventProcessor
    • 🐎 Introduced a new Sequencer class that allows the Disruptor to be applied to other data structures such as multiple arrays. This can be a very useful pattern when multiple event processors work on the same event and you want to avoid false sharing. The Diamond for FizzBuzz is a good example of the issue. It is also higher performance by avoiding the pointer indirection when arrays of primitives are used.
    • 🐎 Further increased performance and scalability by reducing false sharing.
    • ➕ Added progressive backoff strategy to the MultiThreadedClaimStrategy to prevent publisher getting into the claim cycle when the buffer is full because of a slow EventProcessor.
    • 🐎 Significantly improved performance to WaitStrategy.Option.BLOCKING
    • Introduced SequenceGroup to allow dynamic registration of EventProcessors.

  • v2.0.2 Changes

    • 🐎 Rework of "False Sharing" prevention which makes the performance much more predictable across all platforms. Special thanks to Jeff Hain for helping focus in on a solution.