You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MQE: label each source of memory consumption to make it easier to identify where something is returned to the pool multiple times (#11654)
* Introduce `MemoryConsumptionSource` type
* Label each source of memory consumption to make it easier to identify where something is returned to the pool multiple times
* Code review changes
Signed-off-by: Nick Pillitteri <[email protected]>
---------
Signed-off-by: Nick Pillitteri <[email protected]>
Co-authored-by: Nick Pillitteri <[email protected]>
require.NoError(t, memoryConsumptionTracker.IncreaseMemoryConsumption(types.FPointSize*6)) // We have 6 FPoints from the inner series.
48
+
require.NoError(t, memoryConsumptionTracker.IncreaseMemoryConsumption(types.FPointSize*6, limiter.FPointSlices)) // We have 6 FPoints from the inner series.
require.NoError(t, memoryConsumptionTracker.IncreaseMemoryConsumption(types.FPointSize*6)) // We have 6 FPoints from the inner series.
118
+
require.NoError(t, memoryConsumptionTracker.IncreaseMemoryConsumption(types.FPointSize*6, limiter.FPointSlices)) // We have 6 FPoints from the inner series.
// - there's no guarantee the slice will have size 'size' when it's returned to us in putWithElementSize, so using 'size' would make the accounting below impossible
0 commit comments