synchronizers: CountDownLatch vs CyclicBarrier vs Phaser vs Semaphore
One three-round worker pipeline implemented with CountDownLatch (one latch per round), CyclicBarrier (reusable, with a barrier action), and Phaser (reusable, plus dynamic mid-run registration), alongside Semaphore solving the genuinely different problem of bounding concurrent access. Covers timeout behavior (CyclicBarrier permanently breaks on one timeout, Phaser doesn't) and virtual-thread compatibility, including the corrected finding that Object.wait() releases its monitor and never pinned, unlike Thread.sleep() inside synchronized. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01FhzLY5p6okFva3qsnsRyvM
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
$ java PhaserPipeline
|
||||
|
||||
worker-0: finished round 1
|
||||
worker-1: finished round 1
|
||||
worker-2: finished round 1
|
||||
worker-3: finished round 1
|
||||
phaser onAdvance: phase 1 complete, 4 registered parties -> advancing
|
||||
worker-4: registers after round 1 (phaser now has 5 parties)
|
||||
worker-0: finished round 2
|
||||
worker-1: finished round 2
|
||||
worker-2: finished round 2
|
||||
worker-3: finished round 2
|
||||
worker-4: finished round 2
|
||||
phaser onAdvance: phase 2 complete, 5 registered parties -> advancing
|
||||
worker-0: finished round 3
|
||||
worker-1: finished round 3
|
||||
worker-2: finished round 3
|
||||
worker-3: finished round 3
|
||||
worker-4: finished round 3
|
||||
phaser onAdvance: phase 3 complete, 5 registered parties -> advancing
|
||||
done
|
||||
Reference in New Issue
Block a user