-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
perf_hooks: make the event loop display histogram disposable #58384
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
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #58384 +/- ##
==========================================
+ Coverage 90.19% 90.21% +0.01%
==========================================
Files 635 635
Lines 187241 187246 +5
Branches 36768 36767 -1
==========================================
+ Hits 168883 168923 +40
+ Misses 11134 11091 -43
- Partials 7224 7232 +8
🚀 New features to boost your workflow:
|
This comment was marked as outdated.
This comment was marked as outdated.
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.
Same note as #58385 (review): this could be split into two commits for straightforwarder porting to previous release lines.
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.
Code-wise LGTM. But I'm not sure how this will be used in real world.
From a quick search (https://github.com/search?type=code&q=%3D+monitorEventLoopDelay+language%3AJavaScript+OR+language%3ATypeScript), I could not reason about which use case can be improved with using histograom = monitorEventLoopDelay()
. Usually, a histogram might be closed in a different function scope (e.g. triggered by another event).
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
0f65fed
to
4381c85
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
PR-URL: #58384 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: #58384 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Landed in 73471bd...19e0d47 |
PR-URL: #58384 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: #58384 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Fairly self-explanatory, but see the test for an example.