Repository navigation
Language support: run-cache reasons carry measured timings for the five languages without one - #559
Merged
Merged
Conversation
…d tool cache would save per run in Rust, JavaScript, TypeScript, Ruby, PHP and Python, measured on one real project each, so the support page says which of them is worth building for (Rust, and jest) and which is not. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The support page said the benefit of a shared tool cache was "not yet measured" for Rust, JavaScript, TypeScript, Ruby and PHP. This replaces that with timings, one real project per language, and adds a bytecode-cache timing to Python's reason. No behaviour changes:
internal/lang/parity.goreasons and the two generated pages.Measured 2026-11-18 on one 32-core machine, outside the sandbox, median of 3 to 5 runs. "Warm" is a warm cache after one source file changed, which is what a planted fault is.
41a8708,cargo testd3e43be, jest 22.4f06c800, vitest 4.1271c277, pytest7a16331, PHPUnit, OPcache file cachee4aaac1, rspecNot covered: nothing was measured inside the jail; one project per language; no large Rust crate; jest 22 is old and 3 of dayjs's 794 tests fail on this machine in every run; ts-jest,
tscincremental and bootsnap were not measured.Checks run:
go test ./internal/lang,^TestDocs,gen-language-support.sh --check,gen-record-fields.sh --check, licensing. The whole suite was not run.🤖 Generated with Claude Code