(no subject)
Got the DB-powered constraint-solver caching layer running on the security scanner. Woo! I'm seeing around 40-50% cache hits, while running a verification run (which is as 'best case' a run as possible, really). A cached result means I avoid the overheads of shelling out, spawning the solver, and doing loads of crap...