Skip to content
javabypankaj
HomeLibraryPopularCommunity
05
Concurrency & Multithreading
22 topics · 127 questions
1Thread Basics & Overview0/772Synchronization0/883volatile0/554Race Conditions0/335Deadlock, Livelock & Starvation0/446wait/notify, sleep/yield & Producer-Consumer0/667Atomic Classes & CAS0/448Locks: ReentrantLock, ReadWriteLock, StampedLock0/779Safe Publication & Memory Model0/5510Thread Pool & Executor Framework0/8811Thread Pool: Sizing & Pitfalls0/7712ThreadLocal & Thread Confinement0/6613Daemon Threads & JVM Shutdown0/3314CompletableFuture & Resilience0/191915Synchronization Utilities: Latch, Barrier, Semaphore0/6616ForkJoinPool & Work Stealing0/5517Concurrent Collections0/3318Thread Lifecycle: Priority, Interruption, Factory0/5519Thread Troubleshooting0/5520Reactive & Flow API0/2221Benchmarking & Load Testing0/4422Advanced: Disruptor, Actor, False Sharing0/5
1Thread Basics & Overview72Synchronization83volatile54Race Conditions35Deadlock, Livelock & Starvation46wait/notify, sleep/yield & Producer-Consumer67Atomic Classes & CAS48Locks: ReentrantLock, ReadWriteLock, StampedLock79Safe Publication & Memory Model510Thread Pool & Executor Framework811Thread Pool: Sizing & Pitfalls712ThreadLocal & Thread Confinement613Daemon Threads & JVM Shutdown314CompletableFuture & Resilience1915Synchronization Utilities: Latch, Barrier, Semaphore616ForkJoinPool & Work Stealing517Concurrent Collections318Thread Lifecycle: Priority, Interruption, Factory519Thread Troubleshooting520Reactive & Flow API221Benchmarking & Load Testing422Advanced: Disruptor, Actor, False Sharing5
22 topics127 Qs0%
01Core Java17002OOP3203Collections6704Exception Handling2805Concurrency & Multithreading12706Java Streams, Lambda & Functional Programming32807Spring & Spring Boot2608Transactions3209JPA & Hibernate6910Microservices19411Kafka & Messaging9112DevOps, CI/CD & Tooling13313Database & SQL14114REST API & Web4015Design Patterns & LLD5716Advanced Java7117Coding Problems: DSA49218AWS & Cloud4119Data Engineering19420QA, Testing & SDET4121System Design3522Security2023Behavioral / HR: STAR Method37
22Topics
127Questions
0%Complete
22 of 22 topics
Topics
1Thread Basics & Overview0/772Synchronization0/883volatile0/554Race Conditions0/335Deadlock, Livelock & Starvation0/446wait/notify, sleep/yield & Producer-Consumer0/667Atomic Classes & CAS0/448Locks: ReentrantLock, ReadWriteLock, StampedLock0/779Safe Publication & Memory Model0/5510Thread Pool & Executor Framework0/8811Thread Pool: Sizing & Pitfalls0/7712ThreadLocal & Thread Confinement0/6613Daemon Threads & JVM Shutdown0/3314CompletableFuture & Resilience0/191915Synchronization Utilities: Latch, Barrier, Semaphore0/6616ForkJoinPool & Work Stealing0/5517Concurrent Collections0/3318Thread Lifecycle: Priority, Interruption, Factory0/5519Thread Troubleshooting0/5520Reactive & Flow API0/2221Benchmarking & Load Testing0/44
22Advanced: Disruptor, Actor, False Sharing0/55

Advanced: Disruptor, Actor, False Sharing

Concurrency & Multithreading·Topic 22 of 22·5 questions
Q1Two threads print 1,A,2,B,3,C alternately?

Two threads alternate output (1,A,2,B,3,C) by sharing a boolean flag protected with synchronized, wait(), and notify(), where each thread flips the flag after printing and wakes the other.

Read Answer
Q2What is false sharing?

False sharing is a performance problem where two threads writing to independent variables on the same CPU cache line cause constant cross-core cache invalidation, degrading throughput by 10-100x even though no data is actually shared.

Read Answer
Q3What is busy-waiting?

Spinning trades CPU cycles to avoid a context switch, so it helps only for very short waits on an available core; use Thread.onSpinWait to hint the CPU, and block instead when the wait is long or cores are scarce.

Read Answer
Q4What is the LMAX Disruptor?

The Disruptor is a lock-free, pre-allocated ring buffer coordinated by sequences and barriers under a single-writer rule, giving millions of events per second without BlockingQueue lock and allocation overhead.

Read Answer
Q5What is the Actor model?

An actor owns private state, receives asynchronous immutable messages into a mailbox, and processes them one at a time, so shared mutable state and locks disappear entirely.

Read Answer
Previous · Topic 21Benchmarking & Load Testing4 questions
javabypankaj© 2026 javabypankaj
PrivacyTerms
HomeSearchLibrary