-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[PyTorch] [Model Tracer] Use c10::Synchronized<T> for build features tracer #73725
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
Conversation
…tracer Currently, the build features tracer relies on the user to for advisory locking of the mutex when accessing shared data structures. This changes it to be mandatory locking using the `c10::Synchronized<T>` abstraction. Differential Revision: [D34604066](https://our.internmc.facebook.com/intern/diff/D34604066/) [ghstack-poisoned]
CI Flow Status⚛️ CI FlowRuleset - Version:
|
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 557ee24 (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
…tracer Currently, the build features tracer relies on the user to for advisory locking of the mutex when accessing shared data structures. This changes it to be mandatory locking using the `c10::Synchronized<T>` abstraction. Differential Revision: [D34604066](https://our.internmc.facebook.com/intern/diff/D34604066/) ghstack-source-id: 150407248 Pull Request resolved: #73725
…d features tracer" Currently, the build features tracer relies on the user to for advisory locking of the mutex when accessing shared data structures. This changes it to be mandatory locking using the `c10::Synchronized<T>` abstraction. Differential Revision: [D34604066](https://our.internmc.facebook.com/intern/diff/D34604066/) [ghstack-poisoned]
…tracer (#73725) Summary: Pull Request resolved: #73725 Currently, the build features tracer relies on the user to for advisory locking of the mutex when accessing shared data structures. This changes it to be mandatory locking using the `c10::Synchronized<T>` abstraction. ghstack-source-id: 150407248 Test Plan: Built model tracer successfully using: ``` buck build -c pt.disable_per_op_profiling=0 -c pt.enable_record_kernel_dtype=1 --show-output xplat/caffe2/fb/model_tracer:model_tracer ``` Reviewed By: JacobSzwejbka Differential Revision: D34604066 fbshipit-source-id: 29c5c23264f7bd7e13d0fb9dbc218af5663d06e9
|
This pull request has been reverted by 747c6fd. To re-land this change, please open another pull request, assignthe same reviewers, fix the CI failures that caused the revert and make sure that the failing CI runs on the PR by applying the proper ciflow label (e.g., ciflow/trunk). |
|
This pull request has been reverted by 747c6fd. To re-land this change, please open another pull request, assignthe same reviewers, fix the CI failures that caused the revert and make sure that the failing CI runs on the PR by applying the proper ciflow label (e.g., ciflow/trunk). |
Stack from ghstack (oldest at bottom):
Currently, the build features tracer relies on the user to for advisory locking of the mutex when accessing shared data structures. This changes it to be mandatory locking using the
c10::Synchronized<T>abstraction.Differential Revision: D34604066