-
Notifications
You must be signed in to change notification settings - Fork 88
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
Update unit as inference/sec #2352
Conversation
As a user, I am trying to enable the unit self-explanatory. Usually, we see unit format as <some value> <what the value for>/<time>. Example: X images/sec, X frames/sec or etc where images or frames helping user to understand , what the value for. Below Rate unit, until, I read doc or check with owner, I am not sure what it means. Just for a layman, if we keep like below, they might not get it. Rate: X/sec But, if we keep, X inference/sec, it will help clearly to know what this value for. The Rate is how many inferences of the given inputs can be processed per second so X inference/sec will help user for the same. For advance user, it /sec might be ok but I am trying to cover all.
Codecov Report
@@ Coverage Diff @@
## develop #2352 +/- ##
========================================
Coverage 91.36% 91.36%
========================================
Files 440 440
Lines 16530 16530
========================================
Hits 15101 15101
Misses 1429 1429
|
This build is not recommended to merge 🔴 |
🔴torchvision-inceptionv3_1: FAILED: MIGraphX is not within tolerance - check verbose output🔴slim-inceptionv4_1: FAILED: MIGraphX is not within tolerance - check verbose output🔴bert_base_cased_fp16: FAILED: MIGraphX is not within tolerance - check verbose output🔴bert_large_uncased_fp16: FAILED: MIGraphX is not within tolerance - check verbose output🔴distilgpt2_fp16: FAILED: MIGraphX is not within tolerance - check verbose output |
Co-authored-by: Umang Yadav <[email protected]>
Hi @causten @umangyadav After that need to put the same in master and later 6.0 release branch |
This formatting looks wrong. Before it was /sec, which is fine to not have a space between the number. But now we need to modify it as such:
|
I agree...
Honestly it would parse a lot easier if it looked like...
|
I like that better. also i'll need to change my script to reflect this change now. I'll do that now. |
Rate (inf/sec): 1337.84
After that we need to also modify our automation code. cc: @umangyadav @causten |
As a user, I am trying to enable the unit self-explanatory.
Usually, we see unit format as /. Example: X images/sec, X frames/sec or etc where images or frames helping user to understand , what the value for.
Below Rate unit, until, I read doc or check with owner, I am not sure what it means. Just for a layman, if we keep like below, they might not get it. Rate: X/sec
But, if we keep, X inference/sec, it will help clearly to know what this value for. The Rate is how many inferences of the given inputs can be processed per second so X inference/sec will help user for the same.
For advance user, it /sec might be ok but I am trying to cover all.