MuhammadLab

Multiprocessing Simulator

Visualize how CPUs, cores, threads, parallel work, and overhead influence estimated runtime and speedup.

Visual learning • Interactive controls • Parallel speedup insights

Simulation model. This is an educational visualization (not a real benchmark). It uses a consistent timing model across stats, animation, and charts.
Controls
Adjust parameters and watch the model update instantly.
Serial fraction limits speedup (Amdahl’s Law).
Models synchronization/coordination cost as threads increase.
Machine view
This visual maps “workers” onto cores. It’s a teaching model, not a hardware benchmark.
Phase: serialThreads: 8No waiting
CPU 1
8 cores
Total cores
8
CPUs × cores per CPU
Effective workers
8
min(threads, total cores)
Estimated time
265.0 units
Serial + parallel + overhead
Speedup vs 1 thread
3.77×
Efficiency: 47.17%
Phase visualization
Serial → Parallel → Overhead. See where time is being spent.
Current: Serial work (0.00%)
Serial150.0 (56.60%)
Parallel106.3 (40.09%)
Overhead8.75 (3.30%)
Insights
  • - Overhead grows with thread count and reduces parallel benefit.
  • - Cores are saturated — additional threads won’t increase effective workers.
Why this speedup happened
This is a conceptual model — it estimates runtime behavior, not a real benchmark.
This workload is highly parallel, so more effective workers usually reduce runtime — until cores saturate.
Thread count matches total cores — this often produces efficient parallel utilization for compute-bound workloads.
Increasing threads also increases coordination overhead in this model. Past a point, overhead can outweigh parallel gains.
A CPU is a processor package. Cores are execution units. Threads are software workers. In this model, only effective workers (up to core count) run in parallel.
Saved configurations
Add configs to compare time and speedup.
No saved configurations yet. Click Add configuration to build a comparison set.
Estimated time by configuration
Add configurations to generate charts.
Speedup by configuration
Add configurations to generate charts.

Processed Locally

Your file never leaves your device. Everything is processed in your browser — we never see or store your data.