Living City

every car, junction, light and district is a Picard actor offline

Scenario A · Concurrency

Starts with 100 target vehicles, split across active districts. Spawned in batches so the UI never blocks.

Scenario B · Surge

Scenario C · Districts

Click a district to select it. Add or remove it at runtime: its whole actor subtree is created or stopped.

Metrics

runtime from Picard events or the OS · app counted by the demo

About the data

Mailbox depth is not exposed by Picard, so it is not shown. Tick delay is the real time a tick message spends between being sent and handled by a sampled vehicle (about 1 in 16). CPU and memory come from /proc.

movingwaitingcrossingparked

scroll to zoom · shift/right-drag to pan · double-click to reset view · click to inspect · ctrl-click or drag a box to select several

Messages processed/s app

Tick delay mean / p95 µs sampled

Trips/s · % waiting app

CPU % · memory MB process