Repository navigation
Improve cached type checks by up to 55x - #74
Merged
Merged
Conversation
timacdonald
marked this pull request as ready for review
October 30, 2026 04:22
jamesdangercarpenter
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tl;dr; Improve caching performance by up to 55x
Problem
FileCache::hasandFileCache::getboth callFileCache::all, which reads the entire cache file under a lock.A run checks every file with
hasANDget, so a fully cached run includes the cache file twice per analysed file.On a project with ~4,200 files the cache file is ~800KB and each include takes ~6ms, so a fully cached run spends most of its time re-reading the cache.
This keeps the cache contents in memory after the first read.
persistandflushclear them, so the next read loads the file again.Writes still go to disk under the lock as before, so forked workers still merge their results.
Benchmarks
Laravel application with 4,179 analysed files, 11 cores, two rounds each:
The JSON report was identical across every run. A file with missing types reported the same uncovered lines from a cold run, from the cache, and after being changed while every other file was cached.