using worker_id instead of pid will produce fewer db files #430
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.
As the program is restarted frequently, more and more db files will be generated. These files are cumbersome to manage, and aggregate metrics also consume resources.
If the worker id is used as the db file naming method, as long as the number of wokers is determined and the metric type is unchanged, the number of generated db files will not increase, but the values in the file are changing.
this will slow down the prometheus scrape duration.