Benchmark data shows the three-file shard format (.calls, .deps, .impact) dramatically outperforms the single .graph format:
| Format |
Time |
Tool uses |
vs baseline |
| No shards |
827s |
190 |
— |
| Single .graph |
754s |
142 |
-9% time |
| Three files |
264s |
42 |
-68% time |
The three-file format is what graph-fusion (`supermodel-sidecars`) uses. Each file contains one relationship type, so grep hits are more targeted — the agent gets call data when searching for function names, dependency data when searching for imports, impact data when checking blast radius.
Add a `--three-file` flag (or `--format calls-deps-impact`) to `supermodel analyze` that generates three shard files per source file instead of one combined `.graph` file.
Consider making three-file the default based on the benchmark results.
Benchmark data shows the three-file shard format (.calls, .deps, .impact) dramatically outperforms the single .graph format:
The three-file format is what graph-fusion (`supermodel-sidecars`) uses. Each file contains one relationship type, so grep hits are more targeted — the agent gets call data when searching for function names, dependency data when searching for imports, impact data when checking blast radius.
Add a `--three-file` flag (or `--format calls-deps-impact`) to `supermodel analyze` that generates three shard files per source file instead of one combined `.graph` file.
Consider making three-file the default based on the benchmark results.