-
Notifications
You must be signed in to change notification settings - Fork 323
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
[Execuotrch][cpuinfo] Add util to find out # of performant cores #2350
Conversation
This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/2350
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 2a8ee89 with merge base e98a7e0 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D54766068 |
… cores" This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/) [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D54766068 |
… cores" This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/) [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D54766068 |
… cores" This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/) [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D54766068 |
Pull Request resolved: #2350 This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used ghstack-source-id: 218743677 @exported-using-ghexport Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/)
… cores" This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/) [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D54766068 |
… cores" This helps with identifying the # of performant cores which will later be used when reseting the threadpool or using the guard to figure out how many threads should be used Differential Revision: [D54766068](https://our.internmc.facebook.com/intern/diff/D54766068/) [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D54766068 |
This pull request has been merged in e65358c. |
Stack from ghstack (oldest at bottom):
This helps with identifying the # of performant cores which will later be used
when reseting the threadpool or using the guard to figure out how many threads
should be used
Differential Revision: D54766068