-
Notifications
You must be signed in to change notification settings - Fork 9
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
LB stat files should not be written out every phase and should be marked with a trace event #2388
Labels
Comments
cwschilly
added a commit
that referenced
this issue
Jan 10, 2025
cwschilly
added a commit
that referenced
this issue
Jan 30, 2025
cwschilly
added a commit
that referenced
this issue
Jan 30, 2025
cwschilly
added a commit
that referenced
this issue
Jan 30, 2025
cwschilly
added a commit
that referenced
this issue
Feb 3, 2025
cwschilly
added a commit
that referenced
this issue
Feb 7, 2025
cwschilly
added a commit
that referenced
this issue
Feb 7, 2025
cwschilly
added a commit
that referenced
this issue
Feb 7, 2025
cwschilly
added a commit
that referenced
this issue
Feb 7, 2025
cwschilly
added a commit
that referenced
this issue
Feb 7, 2025
cwschilly
added a commit
that referenced
this issue
Feb 10, 2025
lifflander
added a commit
that referenced
this issue
Feb 13, 2025
…-not-be-written-out-every-phase-and-should-be-marked-with-a-trace-event #2388: LB stat files should not be written out every phase and should be marked with a trace event
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I think we should output them every 100 or so phases, maybe with a user-settable flag? We should mark these with a bracketed trace user event so we know how much it costs.
The text was updated successfully, but these errors were encountered: