Skip to content

Use more aggressive gc thresholds for a big speedup #18306

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 19, 2024
Merged

Use more aggressive gc thresholds for a big speedup #18306

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9a2c625
Use more aggressive gc thresholds, and tune earlier
JukkaL Dec 7, 2024
c85dc0e
Perform tuning later, it seems slightly faster
JukkaL Dec 18, 2024
f9be1de
Merge branch 'master' into faster-tune-gc and simplify
JukkaL Dec 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions mypy/build.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,8 +218,9 @@ def _build(
extra_plugins: Sequence[Plugin],
) -> BuildResult:
if platform.python_implementation() == "CPython":
# This seems the most reasonable place to tune garbage collection.
gc.set_threshold(150 * 1000)
# Run gc less frequently, as otherwise we can spent a large fraction of
# cpu in gc. This seems the most reasonable place to tune garbage collection.
gc.set_threshold(200 * 1000, 30, 30)

data_dir = default_data_dir()
fscache = fscache or FileSystemCache()
Expand Down
Loading