Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add trace mode and trace config entries in trace settings API #7050
Add trace mode and trace config entries in trace settings API #7050
Changes from 5 commits
6c2098a
51d5d1c
7cb82dd
65f98cd
50b2a7c
da03f3e
fafd3db
bb838ee
01dda13
b6005d0
2f69088
d6aea8d
17da4c9
422ffdd
6cb3162
fe35d9b
6685bc1
eda0a6b
d090dad
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is probably due for some cleanup in the near future, where you can encapsulate this growing list of parameters into a struct/class or something if makes sense like:
rather than all the individual args.
However, I think this can be a follow-up cleanup rather than a blocker for this change. Feel free to add a JIRA ticket if you agree.
I think some other sections could probably be condensed or cleaned up as well if encapsulating the fields in an object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I will take this up in the Update PR for
https://jirasw.nvidia.com/browse/DLIS-4795
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Food for thought in the future with Olga, but I found this code misleading to read.
Upon reading it, I naively thought
std::to_string(trace_mode)
would be something like"TRITON"
or"OPENTELEMETRY"
, but it's actually "0" or "1" based on order in the enum.InferenceTraceModeString
is the one that actually converts to a string.TLDR; I found it confusing that the keys in this map are "0" and "1" rather than the actual string versions of the modes. The keys in the map could probably just be the enums themselves (TRACE_MODE_TRITON or TRACE_MODE_OPENTELEMETRY [interpreted as integer 0 or 1] rather than string 0 or 1), or the actual string representations ("triton" and "opentelemtry").
No action here, just mentioning something I found misleading to think about down the line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not only trace mode, IIRC, for global settings the key is an empty string