Why benchmark?
A great metric in isolation is meaningless. Benchmarking puts your design next to known references so 'good' has a number. CrystalSim's Benchmarks module compares your saved designs against published silicon (Apple M4, NVIDIA H100, Intel Lunar Lake) and against research devices (Tokyo InGaOx GAA, Georgia Tech piezotronic).
Match metric to application
- AI workloads (datacenter): TOPS, perf/area, memory bandwidth. - Mobile / edge AI: TOPS/W first, then TOPS/mm². - High-performance computing: raw FLOPS, sustained perf/W under load, thermal headroom. - IoT / sensors: TOPS/W and quiescent power dominate; absolute throughput barely matters.
Rule: define the application before opening the benchmark page. Otherwise you'll cherry-pick the metric that flatters you.
Exercise — Crystal-EM vs the world
1. Open the Chip Builder, load the Crystal-EM Hybrid template (Templates menu). 2. Run the full test suite in the Test Lab. 3. Open Benchmarks. 4. Stack your design up against Apple M4 and Tokyo InGaOx GAA. 5. Read the radar chart and table side-by-side.
Reading the result
Crystal-EM should typically win on TOPS/W (resonant gating + lower V_dd) and lose on absolute TOPS until volume manufacturing matures (low TRL + small dies). Use that pattern in your write-up: 'Crystal-EM wins where energy is the bottleneck, loses where raw throughput dominates.' That sentence is honest, defensible, and points to the next R&D step.
- Use the Benchmarks module to put your design next to real silicon.
- Match the right metric to the right application.
- Read where Crystal-EM wins and where it still loses.
- Treat benchmarks as questions, not answers.