Re: [I] Unique identifier for MemoryConsumer and MemoryReservation [datafusion]

["EmilyMatt (via GitHub)" <gi...@apache.org>]

EmilyMatt commented on issue #15126:
URL: https://github.com/apache/datafusion/issues/15126#issuecomment-2782446185

   After looking into this, it seems the Reservation is slightly redundant, since a split_off function can be called which will create a reservation with a certain size, making per-reservation memory tracking in the pool not really applicable without major work, however, I think having an ID in the MemoryConsumer is unobtrusive and provides much more insight and control over memory allocations within a partition


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org