Performance Benchmarks v7.0
1.28ms post-quantum auth (AWS Graviton4). H33 ZKP Stark Lookup prove: 2.0µs, verify: 0.2µs (2.09ns Cachee cached). 12.5× faster than SEAL's FHE pipeline. All benchmarks verified on AWS Graviton4.
Benchmark Methodology
- Instance: AWS c8g.metal-48xl (96 cores, AWS Graviton4, Neoverse V2)
- Optimization: NEON SIMD (AArch64) with Montgomery NTT — 44% faster transforms
- Framework: Criterion.rs with 100+ iterations, 5-second measurement windows
- Caching: Redis 7.1 ElastiCache (0.8ms latency)
- Standards: NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA)
Benchmark Reports
Post-Quantum Production Stack: 1.28ms full crypto auth on Production ARM hardware. BFV Encrypt (420µs) + FHE Inner Product (260µs) + Threshold Decrypt (330µs) + Dilithium Sign+Verify (106µs). H33 ZKP Stark Lookup prove: 2.0µs, verify: 0.2µs (2.09ns Cachee cached). 12.5× faster than Microsoft SEAL. View full methodology →
14-phase benchmark covering post-quantum cryptography, FHE operations, ZK-STARK proofs, batch processing, key pools, caching systems, and trust score engine. 100% of performance targets met across all categories.
The Math: 1.28ms Full Crypto Auth (v7.0)
H33 Production Pipeline (Feb 14, 2026 v7.0)
| BFV Encrypt (Q-128) | 420µs | 33% |
| FHE Inner Product | 260µs | 20% |
| Threshold Decrypt | 330µs | 26% |
| H33 ZKP Stark Lookup | ~2µs | <1% |
| Dilithium Sign+Verify | 106µs | 8% |
| FULL AUTH TOTAL | 1,280µs | 100% |
Production ARM hardware (Graviton4). H33 ZKP Stark Lookup prove: 2.0µs, verify: 0.2µs (2.09ns Cachee cached). ~180KB proof.
H33 vs Microsoft SEAL
| Encrypt | 420µs | 680µs | 1.6× |
| FHE Compute | 260µs | 1,530µs | 5.9× |
| Relin (SEAL) / Threshold (H33) | 330µs | 490µs | 1.5× |
| Decrypt | — | 150µs | H33 uses threshold |
| Pipeline Total | 1,280µs | 2,850µs | 2.2× |
Measured: 2.2× faster single-thread (apples-to-apples). At production scale with SIMD batching: 12.5× faster.
Full Stack Throughput Benchmarks (Feb 14, 2026)
Enterprise-scale performance on Production ARM hardware (96-core single-socket Graviton4). Full QR stack: FHE (BFV) + H33 ZKP Stark Lookup + Kyber768 + Dilithium3 + Blockchain Audit
Hardware Tiers
| AWS Graviton4 | Full crypto auth | 1.28ms |
| AWS Graviton4 | Throughput | — |
| Cachee Pipeline (batch-64) | Cached sessions | 497M ops/sec |
Production Pipeline Breakdown (AWS Graviton4)
| Step | Latency | % of Total |
|---|---|---|
| BFV Encrypt (Q-128) | 420µs | 33% |
| FHE Inner Product | 260µs | 20% |
| Threshold Decrypt | 330µs | 26% |
| H33 ZKP Stark Lookup | ~2µs | <1% |
| Dilithium Sign+Verify | 106µs | 8% |
| FULL AUTH TOTAL | 1,280µs | 100% |
Throughput Tiers
| Tier | Latency | Throughput | What It Does |
|---|---|---|---|
| Full Crypto Auth | 1.28ms | — | FHE + H33 ZKP Stark Lookup + Dilithium |
| Cached Session | 25.6µs | 497M ops/sec | Cachee L1 hit |
| Biometric (batch-64) | varies | 46K/sec | 512-D encrypted matching |
| H33 ZKP Stark Lookup (batch-64) | varies | ~500K/sec | ZK proof generation |
Note: All numbers from Security Parameters Appendix v4.0 (Feb 14, 2026) on AWS Graviton4.
H33 vs Microsoft SEAL
| H33 Full Pipeline | 1,280µs |
| Microsoft SEAL (FHE only) | 2,850µs |
| Single-Thread Speedup | 2.2× |
| H33 at Scale (96 cores, SIMD batch) | 1,148,018 auth/sec |
| Production Scale Speedup | 12.5× faster |
Cachee L1 Cluster Stats
| Workers | 64 (ports 6380-6443) |
| Read throughput | 497M ops/sec |
| Write throughput | 57K/sec |
| Routing | djb2 hash sticky routing |
| Batch API | 5000 keys/request |