-
Notifications
You must be signed in to change notification settings - Fork 30
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
RFC: Add reasons
#239
base: master
Are you sure you want to change the base?
RFC: Add reasons
#239
Conversation
For JET/SnoopCompile integration, it's likely that the same report will be generated for many different calls. This makes it easy to distill the collection down to a unique set of causes.
We might also want to add a |
JET Benchmark ResultJudge resultBenchmark Report for /home/runner/work/JET.jl/JET.jlJob Properties
ResultsA ratio greater than
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfoTarget
Baseline
Target resultBenchmark Report for /home/runner/work/JET.jl/JET.jlJob Properties
ResultsBelow is a table of this job's results, obtained by running the benchmarks.
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfo
Baseline resultBenchmark Report for /home/runner/work/JET.jl/JET.jlJob Properties
ResultsBelow is a table of this job's results, obtained by running the benchmarks.
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfo
Runtime information
Architecture: x86_64
JET Benchmark ResultJudge resultBenchmark Report for /home/runner/work/JET.jl/JET.jlJob Properties
ResultsA ratio greater than
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfoTarget
Baseline
Target resultBenchmark Report for /home/runner/work/JET.jl/JET.jlJob Properties
ResultsBelow is a table of this job's results, obtained by running the benchmarks.
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfo
Baseline resultBenchmark Report for /home/runner/work/JET.jl/JET.jlJob Properties
ResultsBelow is a table of this job's results, obtained by running the benchmarks.
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfo
Runtime information
Architecture: x86_64
|
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.
yeah, it seems more reasonable to aggregate reports based on the "final" frame of reports for this case.
When analyzing user-level script, it might be better to focus on the "entry" frame (usages) rather than the final frame (definitions), because it's more likely that we're interested in wrong usages of package code.
But as for SnoopCompile integration, our main interest is package development, and then it's more appropriate to see definitions.
FWIW, incoming VSCode integration, I want to setup some interface to switch this behavior, and this "reason" interface may also want to use it. But anyway. I think this can be merged as is for now.
👍 Before I hit merge, I might think about the name a bit more (it was a bit tongue-in-cheek, though it's not dreadful either) and make sure it actually works in practice to fix some issues. For example, I have a sneaking suspicion that we may want to aggregate using the bottom frame and one just above it. |
I made a significant refactor recently. I will try to update this branch as well as SnoopCompile side code later. |
Codecov Report
@@ Coverage Diff @@
## master #239 +/- ##
==========================================
- Coverage 87.67% 86.90% -0.78%
==========================================
Files 9 10 +1
Lines 2021 2039 +18
==========================================
Hits 1772 1772
- Misses 249 267 +18
Continue to review full report at Codecov.
|
For JET/SnoopCompile integration, it's likely that the same report
will be generated for many different calls. This PR makes it easy to
distill the collection down to a unique set of causes.
Here's a demo on JuliaIO/ImageIO.jl#38, from inside that package's test directory:
Output:
(nicer in color, of course)
This comes from 255 separate inference triggers, so it's a big reduction. Of course it's possible that it's too big of a reduction, because there may be more that is relevant than just the final frame.
CC @johnnychen94