maximum_ memory
Note
This page applies only to versions before 8.
For 8.
SingleStore will not allocate more than maximum_
megabytes of memory.SELECT
query’s memory allocations put the memory usage by SingleStore over maximum_
, query execution stops and an error message is generated.
By default, maximum_
is set to 90% of the physical memory on the host, or physical memory minus 10GB, whichever value is greater.
As Kubernetes does not support swap, maximum_
for the Operator is set to 80% of physical memory, or physical memory minus 10 GB, whichever is larger
Query compilations whose allocations exceed this limit will also terminate the server.
SingleStore supports disk spilling.
When a node's memory load is above 75% and in-memory data structures (for the current thread) are at least 100MB, the intermediate result of the operation spills to disk in the data/spill directory.spilling_
and spilling_
, respectively.
Currently, the following query operator(s) can be spilt onto disk:
-
GROUP BY
-
SORT
orORDER BY
Note
Disk spilling must be enabled by setting the engine variable, enable_
to ON
.enable_
.
Last modified: July 31, 2024