# Performance

> How fast avro is: measured numbers, what profiling found, and its benchmark history.

[magmalake](https://magmalake.dev/) [avro](https://magmalake.dev/s/avro)

###  Table and file formats

| Operation | magmalake | Reference |
| --- | --- | --- |
| Avro decode, manifest-shaped records the schema-compiled cursor, 1 core | **18.1M records/s — 25.9M with field selection** | fastavro 1.12.2 on the same file: 1.70M — 10.7× faster |
| Avro inflate | 1.0 GB/s | — |

scroll the table sideways →

Apple M4 — ten cores, four of them performance — macOS, stable Mojo 1.0.0, with nothing else building on the machine. Measured on 5 September 2026; the Iceberg rows on 15 September, the boundary rows on 19 September. [How these were measured](https://magmalake.dev/performance#method).

### Found by profiling

**Avro boxing roughly 60 allocations per record.** And JSON schema parsing turning out to be 72% of the cost of reading a manifest.

Every merge also runs its benchmarks on a GitHub runner: [the benchmark history](https://magmalake.github.io/avro.mojo/benchmarks/). Read it for trends; a shared runner is slower and noisier than the table.

[A magmalake project](https://magmalake.dev/)

Apache 2.0 · © 2026 Marius Seritan