Skip to content
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

Tracking module-level seqio TaskRegistry use back to where the tasks were registered #495

Closed
wants to merge 0 commits into from

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Mar 16, 2023

Tracking module-level seqio TaskRegistry use back to where the tasks were registered

Functionality:
1) New module task_registry_provenance_tracking module-level attribute that determines whether to track
the callsites of TaskRegistry.add calls.
When this attribute is turned on with task_registry_provenance_tracking.turn_on_tracking(), every time TaskRegistry.add is invoked, a portion of the call stack is retained, aiding a debugger's ability to determine "where was the code that registered this task?"

Speed:
Before making changes: 60 seconds for 200k tasks
After making changes: 80 seconds (but the default is off)

@copybara-service copybara-service bot force-pushed the test_513290892 branch 12 times, most recently from ea809ed to d7d897b Compare March 17, 2023 16:03
@copybara-service copybara-service bot closed this Mar 17, 2023
@copybara-service copybara-service bot deleted the test_513290892 branch March 17, 2023 16:13
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.

0 participants