mix aurora_meter.
View Source
Measures Aurora Meter's hot-path throughput: concurrent AuroraMeter.Counter
increments against warm ETS counters (no database on the hot path). This is the
evidence behind the BEAM-metering moat claim.
Each worker increments its own counter key, matching real usage where load is spread across many tenant/feature counters rather than one hot row.
mix aurora_meter.bench # defaults: 8 procs x 500_000 incrs
mix aurora_meter.bench 16 500000