-
Notifications
You must be signed in to change notification settings - Fork 399
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
Limit the number of memory records reported #491
Conversation
03ddecf
to
9243e82
Compare
38d1bde
to
e56b11c
Compare
8cd7bfa
to
fdb1abf
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #491 +/- ##
=======================================
Coverage 92.16% 92.16%
=======================================
Files 91 91
Lines 10872 10898 +26
Branches 1499 1507 +8
=======================================
+ Hits 10020 10044 +24
- Misses 849 851 +2
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
For very big files, the generated reporters will hung when trying to process all of the memory records produced. This happens quite a lot in flamegraphs produced from very big files, where the browser cannot display the ploy with millions of points. To help here, add a new parameter to the FileReader class that limits the number of memory records (and therefore temporal snapshots) stored and reported. This should not affect most regular capture files but will help with the very big ones. Signed-off-by: Pablo Galindo <[email protected]> Co-authored-by: Matt Wozniski <[email protected]> Signed-off-by: Pablo Galindo <[email protected]>
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.
LGTM
No description provided.