-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
vcpkg/cmake/ninja using only efficiency cores under windows #39935
Labels
category:community-triplet
A PR or issue related to community triplets not officially validated by the vcpkg team.
Comments
I don't think this is vcpkg related 😅 Is your Laptop connected to power? |
yes 🤣 |
jimwang118
added
category:community-triplet
A PR or issue related to community triplets not officially validated by the vcpkg team.
and removed
category:question
This issue is a question
labels
Jul 17, 2024
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
Maybe related to microsoft/vcpkg-tool#1555. Can you try this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
category:community-triplet
A PR or issue related to community triplets not officially validated by the vcpkg team.
I have a machine with intel i7-13850hx. Under windows 10 when building it uses only efficient cores, while under wsl2 it uses all cores available.
There's nothing defined from the environment point of view to limit concurrency.
Is it by design on windows (maybe beyond vcpkg control)?
Am I the only one experiencing it?
Environment
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All cores to be used
Failure logs
The text was updated successfully, but these errors were encountered: