HoloVoxel evidence
Detail against components read
One 16 by 16 chunk stored as a single hologram decodes 98.4 percent of its cells correctly at the full budget of 8,192 components, 131,072 bytes and 17.0 ms. Reading fewer components is cheaper and fuzzier: 67.1 percent at 1,568 components, and 19.5 percent at 24, which takes 384 bytes and 0.09 ms.
- One chunk decoded at several budgets
- Losses shown
Headline
- of cells decoded correctly with all 8,192 components
- 98.4%
- less hologram read at 24 components than at the full budget
- 341 times
- less decode time at the smallest budget than at the full one
- 189 times
Where it is slower
Every loss in this record, stated once- Accuracy is low at small budgets by design: 19.5 percent at 24 components, against 12.5 percent for a random guess. A far read is a soft blend, not a smaller copy of the near one.
How it was measured
Stated once, for every figure on this page- Workload
- A chunk of a fixed procedural world is built at full fidelity. For each component budget it is decoded as a colour field and checked cell by cell against the stored block (Chunk.Accuracy). The hologram size is the number of bytes CapacityProbe reports for that budget.
- Engines
- HoloVoxel Chunk.DecodeField at ten component budgets
- Check
- Accuracy is the share of surface cells whose strongest decoded block equals the block that was stored.
- Statistic
- Accuracy is one measurement of one chunk. Decode time is the median of 15 runs after warm-up.
- Memory and logging
- Hologram size is sixteen bytes per component read.
- Ties
- Eight blocks are possible, so a random guess is right 12.5 percent of the time.
Results
| Components read | Cells correct (percent) | Hologram size (bytes) | Decode time (ms) |
|---|---|---|---|
| 24 | 19.5 | 384 | 0.09 |
| 48 | 19.7 | 768 | 0.15 |
| 98 | 23.4 | 1,600 | 0.26 |
| 196 | 28.7 | 3,136 | 0.41 |
| 392 | 34.0 | 6,272 | 0.71 |
| 784 | 49.2 | 12,544 | 1.58 |
| 1,568 | 67.1 | 25,088 | 3.19 |
| 3,136 | 83.3 | 50,176 | 6.25 |
| 6,272 | 96.4 | 100,352 | 13.09 |
| 8,192 | 98.4 | 131,072 | 17.04 |
Limits
- One chunk of one world. Terrain with other block mixes will score differently.
- Accuracy is measured at full resolution for each budget. The scene on the product page also coarsens the grid with distance, which this table does not measure.
- Decode time is for one chunk on one machine.