Home▸Distributed & Parallel Computing▸Edge Offloading: Energy vs Latency Simulator

Edge Offloading: Energy vs Latency Simulator (2D)

Interactive 2D mobile-edge-computing simulator: tune task size, local CPU frequency, wireless bandwidth and an energy-vs-latency policy weight, watch a live bar-chart comparison of local vs. offloaded execution, and see a real decision-boundary map swept from the same offloading equations.

Distributed & Parallel Computing2DModerate60 FPS📱 Mobile-adapted⇄ 3D version

Details

CategoryDistributed & Parallel Computing

RenderingCanvas 2D

DifficultyModerate

Target FPS60

ControlsSliders for task data size, local CPU frequency, wireless bandwidth and an energy-vs-latency policy weight (alpha); buttons to force Always Local, Always Offload, or Adaptive (score-based) decision mode; a Send Task Now button to inject an extra task on demand; and buttons to switch the decision-boundary map between Size x Bandwidth and Size x Frequency axes.

edge-computingdistributed-systemsIoTenergy-latency-tradeoffmobile-computingoffloading

📖 Read the articleThe maths behind Edge Offloading: Energy vs Latency Simulator

Related simulations

Distributed ConsensusRaft consensus algorithm, CAP theorem and Byzantine fault tolerance in distributed systems.

Bloom Filter — Probabilistic Set MembershipA Bloom filter tests set membership with k hash functions over a bit array: no false…

Consistent Hashing — The Hash RingMap keys and servers onto a hash ring so adding or removing a node only remaps a small… ⊞ All 61 in Distributed & Parallel Computing →

Every mobile and IoT device running edge computing faces the same decision, over and over: run this task on local silicon, or send it across the wireless link to a nearby edge server? This 2D build models that choice with the standard mobile-edge-computing offloading equations — local compute time and dynamic CMOS energy (which scales with the square of CPU frequency) versus wireless transmission time plus edge-server compute time and radio energy. Tune task size, local CPU frequency, wireless bandwidth and an energy-versus-latency policy weight, watch tasks route themselves between a local-compute node and an edge server on an animated timeline, read the live bar-chart comparison of predicted time and energy, and inspect a real decision-boundary map — swept cell by cell from the same formulas — showing exactly which region of the parameter space favors local compute versus offloading.

⚙ Under the hood

Adjust task size, CPU freq., and wireless bandwidth to see how they affect local vs. offload decisions, balancing time and energy.

edge-computingdistributed-systemsIoTenergy-latency-tradeoffmobile-computingoffloading

2D · HTML5 Canvas 2D · 60 FPS target · runs fully client-side, no install