[v3-1-test] Do not remove .pyc and .pyo files after building Python (#58944)#58947
Merged
ephraimbuddy merged 1 commit intov3-1-testfrom Dec 2, 2025
Merged
[v3-1-test] Do not remove .pyc and .pyo files after building Python (#58944)#58947ephraimbuddy merged 1 commit intov3-1-testfrom
ephraimbuddy merged 1 commit intov3-1-testfrom
Conversation
…58944) With .pyc files removal after compilation we save very little space. Uncompressed sizes of regular airflow image are: Before 7.63GB After 7.66GB So we have images bigger by < 0.5% And it seems that long running containers without those files can suffer from continuous attempts to recreate the .pyc files that fail due to lack of permissions and cause negative dentries to be continuously created: https://lwn.net/Articles/814535/ Those negative dentries are created by kernel - caching the fact that a file was not available - which speeds up lookup but also takes a bit of memory. It seems that when compiled Python has the .pyc files removed, it tries to recreate them with timestamped entries every time new interpreter is started. While this is not a problem for long running processes - because those interpreters are run exactly once per container, this is a problem if you use `exec` in containers to run Health Checks. Evey health-check creates a new interpreter and every time it is created, a new negative dentries to take kernel memory. By not removing the .pyc files we increase a bit the size of the image but improve a little the startup time (no need to compile Python internal .py files, as well as get rid of the negative dentries problem. This PR likely: (cherry picked from commit bcda508) Co-authored-by: Jarek Potiuk <[email protected]> Fixes: #58509 Fixes: #42195
boring-cyborg
bot
added
area:dev-tools
area:production-image
ephraimbuddy
added
type:misc/internal
ephraimbuddy
requested review from
amoghrajesh,
ashb,
bugraoz93,
eladkal,
gopidesupavan,
jason810496,
jscheffl,
kaxil and
potiuk
as code owners
Lee-W
approved these changes
Dec 2, 2025
bugraoz93
approved these changes
Dec 2, 2025
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 3, 2025
…58944) (#58947) With .pyc files removal after compilation we save very little space. Uncompressed sizes of regular airflow image are: Before 7.63GB After 7.66GB So we have images bigger by < 0.5% And it seems that long running containers without those files can suffer from continuous attempts to recreate the .pyc files that fail due to lack of permissions and cause negative dentries to be continuously created: https://lwn.net/Articles/814535/ Those negative dentries are created by kernel - caching the fact that a file was not available - which speeds up lookup but also takes a bit of memory. It seems that when compiled Python has the .pyc files removed, it tries to recreate them with timestamped entries every time new interpreter is started. While this is not a problem for long running processes - because those interpreters are run exactly once per container, this is a problem if you use `exec` in containers to run Health Checks. Evey health-check creates a new interpreter and every time it is created, a new negative dentries to take kernel memory. By not removing the .pyc files we increase a bit the size of the image but improve a little the startup time (no need to compile Python internal .py files, as well as get rid of the negative dentries problem. This PR likely: (cherry picked from commit bcda508) Fixes: #58509 Fixes: #42195 Co-authored-by: Jarek Potiuk <[email protected]>
78 tasks
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
4 participants
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.
With .pyc files removal after compilation we save very little
space. Uncompressed sizes of regular airflow image are:
Before 7.63GB
After 7.66GB
So we have images bigger by < 0.5%
And it seems that long running containers without those files can
suffer from continuous attempts to recreate the .pyc files that
fail due to lack of permissions and cause negative dentries to
be continuously created:
https://lwn.net/Articles/814535/
Those negative dentries are created by kernel - caching the fact
that a file was not available - which speeds up lookup but also
takes a bit of memory. It seems that when compiled Python has
the .pyc files removed, it tries to recreate them with timestamped
entries every time new interpreter is started.
While this is not a problem for long running processes - because
those interpreters are run exactly once per container, this is
a problem if you use
execin containers to run Health Checks.Evey health-check creates a new interpreter and every time it is
created, a new negative dentries to take kernel memory.
By not removing the .pyc files we increase a bit the size of the
image but improve a little the startup time (no need to compile
Python internal .py files, as well as get rid of the negative
dentries problem.
This PR likely:
(cherry picked from commit bcda508)
Co-authored-by: Jarek Potiuk [email protected]
Fixes: #58509
Fixes: #42195