Skip to content

gh-1542: Do not suggest make -j #1543

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.

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

Closed
wants to merge 1 commit into from

Conversation

Yhg1s
Copy link
Member

@Yhg1s Yhg1s commented Apr 18, 2025

Do not suggest make -j for building CPython. make -j means no limit on

the number of concurrent jobs, not "a sensible limit considering the available memory and CPU cores". With LTO it's easy to run out of memory when too many jobs run at the same time.


📚 Documentation preview 📚: https://cpython-devguide--1543.org.readthedocs.build/

…imit on

the number of concurrent jobs, not "a sensible limit considering the
available memory and CPU cores". With LTO it's easy to run out of memory
when too many jobs run at the same time.
@@ -547,8 +547,11 @@ Now that the configuration is in place, it remains to compile the project:
.. tip::

Use ``make -j`` to speed-up compilation by utilizing as many CPU cores
as possible or ``make -jN`` to allow at most *N* concurrent jobs.
Use ``make -jN`` to speed-up compilation by utilizing as many CPU cores
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Use ``make -jN`` to speed-up compilation by utilizing as many CPU cores
Use ``make -jN`` to speed-up compilation by using as many CPU cores

@Yhg1s
Copy link
Member Author

Yhg1s commented Apr 18, 2025

Closing in favour of #1541.

@Yhg1s Yhg1s closed this Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants