v.22.6Improvement

Set global_memory_usage_overcommit_max_wait_microseconds to 5 seconds and enhance OOM exception message with OvercommitTracker info

Official CH changelog text
Set global_memory_usage_overcommit_max_wait_microseconds default value to 5 seconds. Add info about OvercommitTracker to OOM exception message. Add MemoryOvercommitWaitTimeMicroseconds profile event. #37460 (Dmitry Novik).
Set the default value of global_memory_usage_overcommit_max_wait_microseconds to 5 seconds, enhance OOM exception messages with OvercommitTracker info, and add a new profile event MemoryOvercommitWaitTimeMicroseconds.

Why it matters

This feature improves memory overcommit handling by providing a sensible default wait time for memory overcommit requests, making out-of-memory (OOM) exception messages more informative with details from the OvercommitTracker. Additionally, the new profile event allows monitoring of how long queries wait due to memory overcommit, which helps in performance tuning and troubleshooting.

How to use it

The new default value of global_memory_usage_overcommit_max_wait_microseconds is automatically applied. Users can monitor memory overcommit wait time by querying the MemoryOvercommitWaitTimeMicroseconds profile event. When encountering OOM errors, check exception messages for enhanced OvercommitTracker details to gain insights into memory allocation issues.

Related resources

PreviousNext