-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
chore!: update prometheus-gc-stats dependency #5677
Merged
Merged
Conversation
This file contains 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
wemeetagain
force-pushed
the
cayman/update-prometheus-gc-stats
branch
from
June 21, 2023 16:37
d9ea0d6
to
94fe4c4
Compare
Performance Report✔️ no performance regression detected Full benchmark results
|
wemeetagain
changed the title
chore: update prometheus-gc-stats dependency
chore!: update prometheus-gc-stats dependency
Jun 21, 2023
twoeths
approved these changes
Jun 22, 2023
nflaig
reviewed
Jun 23, 2023
@@ -13,5 +13,7 @@ export function collectNodeJSMetrics(register: Registry, prefix?: string): void | |||
// - nodejs_gc_runs_total: Counts the number of time GC is invoked | |||
// - nodejs_gc_pause_seconds_total: Time spent in GC in seconds | |||
// - nodejs_gc_reclaimed_bytes_total: The number of bytes GC has freed | |||
gcStats(register, {prefix})(); | |||
// `close` must be called to stop the gc collection process from continuing | |||
const close = gcStats(register, {collectionInterval: 6000, prefix}); |
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.
why is the interval every 6 seconds? Is it just randomly selected or is there some reason for that specific value?
This was referenced Jun 23, 2023
Closed
🎉 This PR is included in v1.10.0 🎉 |
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.
Motivation
When updating to node v20, the
gc-stats
package was found to be out of date and incompatible with node 20. This dependency is a sub-dependency ofprometheus-gc-stats
, which we use to gather information about gc runs.While investigating, I found that the information from
gc-stats
is now available natively from thenode:v8
package (as of node v18.15.0).Seeing as
prometheus-gc-stats
was not well maintained, andgc-stats
is completely abandoned, I took this opportunity to simplify the supply chain and use the native functionality fromnode:v8
in a new@chainsafe/prometheus-gc-stats
package (pull requests and a review welcome).Description
@chainsafe/prometheus-gc-stats
instead ofprometheus-gc-stats
.gcStats(...)
now requires cleanup by calling the returned function.