Benchmarks & Performance Analysis

No benchmark results are published in the repository. The project site displays figures such as 847 functions, 62 imports, and 4.1K cross-references, but these are illustrative interface values in a product mockup, not measured benchmarks, and we do not present them as performance data. Real throughput, memory, and accuracy benchmarks require additional validation.

Performance Metrics

Metric	How to measure	Value
Loader latency	Time from open to normalized BinaryImage, per format (PE/ELF/Mach-O), across small/medium/large binaries	Additional validation required
Disassembly throughput	Instructions decoded per second on a representative target	Additional validation required
CFG recovery time	Time to recover functions/blocks/edges for a target of known function count	Additional validation required
Decompiler latency	Time to emit structured output per function, and full-binary total	Additional validation required
Analysis throughput	End-to-end pipeline time (loader→decompiler) per MB of target	Additional validation required
Memory usage	Peak RSS during full analysis, excluding the target under debug	Additional validation required
Database size	On-disk .sqlite project size relative to target size and run count	Additional validation required
Debugger overhead	Added latency per breakpoint hit / single-step	Additional validation required
AI run cost	Requests per run and wall-clock added, at a given max_model_functions	Additional validation required

Performance Analysis

No performance measurements (analysis time per binary, memory footprint, decompiler latency, debugger overhead) are published. Performance analysis is Additional validation required.