Skip to content

Conversation

krajorama
Copy link
Member

Related to #13659 .

Optimize the engine in case the iterator loading histogram samples has already allocated the samples and doesn't modify them afterwards , thus there is no need to make copies. E.g. storageSeriesIterator

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
@krajorama krajorama requested a review from roidelapluie as a code owner March 1, 2024 07:27
@krajorama krajorama marked this pull request as draft March 1, 2024 07:27
@@ -385,7 +387,7 @@ func (it *SampleRingIterator) AtFloatHistogram(fh *histogram.FloatHistogram) (in
it.fh.CopyTo(fh)
return it.t, fh
}
return it.t, it.fh.Copy()
return it.t, it.fh
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this also be guarded behind reuseHistograms?

@bwplotka
Copy link
Member

Hello from the bug scrub! 👋🏽

@krajorama any progress on it or should we close for now?

@krajorama
Copy link
Member Author

I'd like to work on this, please keep open. This is on my backlog for sure.

@krajorama
Copy link
Member Author

Closed in favor of #16879. Should be tackled properly in #16581

@krajorama krajorama closed this Jul 21, 2025
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.

3 participants