Repository navigation
Name blocking code that isn't tracked - #8
Merged
Merged
Conversation
…king calls, inlined and native frames resolved; queueing the app can't see in traceperf run
…on fast CI machines
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
traceperf run(andTRACEPERF_PROFILE_BLOCKING=1withtraceperf/auto) samples the CPU during the synchronous part of blocking calls, soexplainnames the function and line, e.g.CPU time: buildReport (server.js:10) 100%.hashPassword → pbkdf2Sync), and GC pauses are reported as GC.runcompares clients' latency with the app's own timings to report queueing the app can't see (GET /ping took 0.2 ms in the app but clients waited 185 ms).blocking-native. Example-app checks now require the function names. They were stable across repeated runs.