VALIDATION
Validation results and comparison layers.
This page collects measured outputs, comparison logic, and release interpretation behind public benchmark claims.
Wall-clock runtime, clean-binary timing, and cross-system comparison remain separate methodological objects.
Measured logic
The validation layer keeps runtime, comparison method, and release boundary separated for clear interpretation.
- Deterministic execution under ARM64 benchmark conditions
- Comparison against independent computational references
- QA summaries and archive manifests tied to release layer
Cross-system comparison
MAYAN_ALFA measurements are read with MR and primesieve references where stricter comparison is required.
- MR comparison layers
- primesieve validation references
- QA mismatch control
Publication discipline
Public releases remain bounded at 10B; larger runs are handled in controlled archive tiers.
- Public presentation stops at 10B
- Controlled tiers extend archive evidence from 10M to 500B
- Later instrumentation will refine binary timing
Comparison overview
| Limit | MAYAN_ALFA | MR only | PRIMESIEVE | pi(N) | Status |
|---|---|---|---|---|---|
| 10M | 1.684354 s | 3.604905 s | 1.000000 s | 664579 | OK |
| 100M | 0.360000 s | 23.874431 s | 1.000000 s | 5761455 | OK |
| 1B | 1.793206 s | 244.145627 s | 9.000000 s | 50847534 | OK |
| 10B | 18.806417 s | NO PUBLIC MR RUN | 94.000000 s | 455052511 | OK |
| 100B (BRONZE) | — | — | — | — | OK |
| 200B (SILVER) | — | — | — | — | OK |
| 500B (GOLD) | — | — | — | — | OK |
Interpretive note
Measured values represent internal benchmark execution time under specific ARM64 testing conditions and should not be interpreted as universal performance metrics.
Results depend on hardware configuration, compiler optimization, execution methodology, and dataset structure.
All benchmark outputs were cross-validated against independent computational methods and archived within the MAYAN_ALFA validation framework.
