Wez Furlong
42bf5c5e61
We've been hoping that mkdocs-material will ship the much anticipated search enhancements for some time, but it's time to recognize that we need to do something to improve the search results with how things work right now. This is a big commit that changes the titles of the various pages from the code-annotated synopsis to just the name of the function. This makes it much easier now to match things like `kumo.reject` directly, but `reject` remains awkward to find. I think this is the best that we can do at this time. A few functions have been annotated with the `status: deprecated` to show as deprecated in the toc/nav (shows with a little trash can next to the name).
1.0 KiB
tags
| tags | |
|---|---|
|
kumo.set_memory_low_thresh
kumo.set_memory_low_thresh(THRESH)
{{since('2025.03.19-1d3f1f67')}}
Set the low memory threshold. This usually defaults to 60% of amount of physical RAM in the system (actually 80% of the soft limit which happens to be 75% of the physical RAM), but ulimit or cgroup constraints may modify the value.
When the system is using more than the low memory threshold, passive memory reduction measures will be enabled, including releasing message data when messages move between queues.
You might want to modify this value if you have a lot of RAM and want the passive reduction measures to kick in when more of it is in use than the defaults would otherwise allow.
See Memory Management for a discussion on how kumomta manages memory usage.
It is recommend to set this during the pre_init event.
The THRESH is expressed as an integer number of bytes.
kumo.on('pre_init', function()
kumo.set_memory_low_thresh(800 * 1024 * 1024)
end)