Skip to content

Resurrect changes by shappir to improve memory usage of sparse histograms. - #760

Open
jdmarshall wants to merge 2 commits into
prometheus:mainfrom
jdmarshall:shappir
Open

Resurrect changes by shappir to improve memory usage of sparse histograms. #760
jdmarshall wants to merge 2 commits into
prometheus:mainfrom
jdmarshall:shappir

Conversation

@jdmarshall

Copy link
Copy Markdown
Contributor

This resurrects a PR from 2 years ago written by @shappir to work on top of the storage engine changes that are landing in 0.16

This also includes a bug fix for #616

This looks to be a few % faster than what is currently on trunk. I'm unclear on how much this improves memory efficiency, but this should be fine.

Comment thread CHANGELOG.md Outdated
- AggregatorRegistry renamed to ClusterRegistry, old name deprecated
- chore: update faceoff to 1.1
- perf: Stat aggregation uses similar strategy to collection. 60% faster aggregation
- fix: Avoid updating exemplar values during subsequent metric changes (Fixes [#616](https://github.com/prometheus/client_js/issues/616))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#616 was marked fixed in v15.1.1 and this line is already in the changelog.

Comment thread CHANGELOG.md Outdated
- chore: Add copyright license headers and test
- Make cluster and worker-thread metric aggregation order deterministic
- Export `MetricObject`, `MetricObjectWithValues`, `MetricValue` and `MetricValueWithName` from the TypeScript definitions
- perf: Improvet the memory usage of histograms by delaying allocation of bucket data

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- perf: Improvet the memory usage of histograms by delaying allocation of bucket data
- perf: Improve the memory usage of histograms by delaying allocation of bucket data

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Github merge let me down. Not sure what happened here. Forcing back to previous

Comment thread CHANGELOG.md

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if you always use the "create merge commit" merge method, but the second commit is basically empty/has the wrong commit message and could be rebased out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants