Remove unused samples.thread column#6151
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6151 +/- ##
=======================================
Coverage 83.49% 83.49%
=======================================
Files 344 344
Lines 36882 36870 -12
Branches 10241 10335 +94
=======================================
- Hits 30793 30783 -10
+ Misses 5661 5660 -1
+ Partials 428 427 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
canova
left a comment
There was a problem hiding this comment.
Ah weird. Yeah, I think we wanted to show which samples came from which thread at some point. But better to remove it.
| // Legacy: older profiles produced by merging may have a per-sample | ||
| // origin-thread column. Not written by current code, but tolerated on | ||
| // input so pre-existing profiles still parse. |
There was a problem hiding this comment.
Do we still need to keep these types here? Isn't it better to remove them so we can make sure that they are not used by mistake later?
Also this part of the comment doesn't make sense: "... but tolerated on input so pre-existing profiles still parse". We don't usually care if a table has extra columns.
There was a problem hiding this comment.
Oh yes that comment indeed makes no sense.
I was torn on whether to remove the fields from the types. I thought that maybe in the future we might want to have an upgrader that takes that information from old profiles which had it... nevermind, typing it out I realize that this is not going to happen. It's rare for somebody to use the comparison view and even rarer that they would upload the comparison profile. I'll clean this up.
| // Legacy: older profiles produced by merging may have a per-sample | ||
| // origin-thread column. Not written by current code, but tolerated on | ||
| // input so pre-existing profiles still parse. | ||
| threadId?: Tid[]; |
7bc758e to
e889c59
Compare
This was added by the merging/diffing code and propagated in various places, but never actually read. There is a possibility that we may want to make use of this field in the future, but it's been many years and it hasn't happened, so let's just remove it for now. We can always add it back once we need it.
e889c59 to
31bd60e
Compare
<!-- profiler-preview-links:start --> [Main](https://main--perf-html.netlify.app/) | [Deploy preview](https://deploy-preview-6174--perf-html.netlify.app/) <!-- profiler-preview-links:end --> The auto-rebase of #6151 over #6168 caused a typecheck failure and auto-merge merged anyway. I've now added the "typecheck (ubuntu-latest)" task to the required passing tasks in the branch protection rules so this shouldn't happen again.
Main | Deploy preview
This was added by the merging/diffing code and propagated in various places, but never actually read. There is a possibility that we may want to make use of this field in the future, but it's been many years and it hasn't happened, so let's just remove it for now. We can always add it back once we need it.
I noticed it because it ends up in the "compact" speedometer profiles from CI via
profiler-edit --merge-non-overlapping-threads-by-name.