Important
New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.
MV_ SYSINFO_ CPU
This view describes the total CPU usage breakdown of SingleStore Helios and other processes per node.
|
Column name |
Description |
|---|---|
|
|
The ID of the node. |
|
|
The IP address of the node. |
|
|
The port on which the node is listening. |
|
|
|
|
|
CPU usage by the SingleStore Helios process since its startup. |
|
|
CPU usage by the SingleStore Helios process, in user mode, since process startup. |
|
|
CPU usage by the SingleStore Helios process, in kernel mode, since process startup. |
|
|
CPU usage since the startup of the machine. |
|
|
CPU usage in user mode since the startup of the machine. |
|
|
CPU usage in nice mode since the startup of the machine. |
|
|
CPU usage in kernel mode since the startup of the machine. |
|
|
CPU idle time since the startup of the machine. |
|
|
CPU waiting time for I/O since the startup of the machine. |
|
|
Time spent on servicing interrupts. |
|
|
Time spent on servicing soft interrupts. |
|
|
Stolen time, which is the time spent in other operating systems when running in a virtualized environment. |
|
|
Time spent running a virtual CPU for guest operating systems under the control of the Linux kernel. |
|
|
Time spent running a nice guest (virtual CPU for guest operating systems under the control of the Linux kernel). |
|
|
The amount of time in nanoseconds that the cgroup (that this SingleStore Helios process is a member of) is allowed to spend per |
|
|
Used in conjunction with |
|
|
The number of cores on host. |
|
|
The time when the data was received. |
The system-wide CPU columns (TOTAL_, USER_, SYSTEM_, IDLE_, IOWAIT_, IRQ_, SOFTIRQ_, STEAL_, GUEST_, and GUEST_) report host-level metrics from /proc/stat.
To measure CPU usage for your SingleStore process, use the MEMSQL_, MEMSQL_, and MEMSQL_ columns.
The CFS_ and CFS_ columns report the cgroup CPU limits assigned to your cluster.
Last modified: