This guide explains how to keep Vibgrate scans fast and how to control caching with the --no-cache flag. It is for developers and CI engineers tuning scan time without sacrificing accuracy.
Overview
The Vibgrate CLI uses caching to avoid redoing work on repeated scans, which makes the second and later runs faster. Most of the time the cache is exactly what you want. Occasionally you need a clean run, and that is what --no-cache is for.
Running a fast repeated scan
A normal scan benefits from the cache automatically:
vg
Forcing a clean run
When you want to ignore the cache and recompute from scratch, for example to rule out a stale result while debugging, pass --no-cache:
vg scan --no-cache
Keeping feedback quick
For fast per-change feedback, scope the scan to what changed with --changed-only, then run a full scan periodically for the authoritative number. See the scanning only changed files guide.
Tips
- Leave caching on for everyday and CI scans; it is the faster default.
- Reach for
--no-cacheonly when you suspect a stale result and want a definitive recompute. - Exclude large generated or vendored directories with
--excludeto reduce work.
Related
See the scanning only changed files guide, the scanning large repositories guide, the excluding paths guide, and the scan command reference.