Skip to content

Expose used MemoryPool details in ResourcesExhausted error messages #20386

@erenavsarogullari

Description

@erenavsarogullari

Is your feature request related to a problem or challenge?

memory_limit (RuntimeEnvBuilder::new().with_memory_limit()) configuration uses greedy memory pool as default. However, if memory_pool (RuntimeEnvBuilder::new().with_memory_pool()) is set, it overrides by expected memory_pool config such as fair. Also, if both memory_limit and memory_pool configs are not set, then unbounded memory pool is being used so it can be useful to expose ultimately used/selected pool as part of Resources Exhausted error message for the end user awareness and the user may need to switch used memory pool (greedy, fair, unbounded),

  • Also, this comparison table is an example use-case for both greedy and fair memory pools runtime behaviors and this addition can help for this kind of comparison table by exposing used memory pool info as part of native logs.

Describe the solution you'd like

  • Adding name property to MemoryPool instances,
  • Expose used MemoryPool info to Resources Exhausted error messages.

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Labels

enhancementNew feature or request
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions