Sign inTry Free

MV_SYSINFO_CPU

This view describes the total CPU usage breakdown of SingleStore and other processes per node.

Column name

Description

node_id

The ID of the node.

ip_addr

The IP address of the node.

port

The port on which the node is listening.

type

MA, Leaf, or CA

memsql_total_cumulative_ns

CPU usage by the SingleStore process since its startup.

memsql_user_cumulative_ns

CPU usage by the SingleStore process, in user mode, since process startup.

memsql_system_cumulative_ns

CPU usage by the SingleStore process, in kernel mode, since process startup.

total_used_cumulative_ns

CPU usage since the startup of the machine. It refers to the whole machine, and not to SingleStore cgroup.

user_used_cumulative_ns

CPU usage in user mode since the startup of the machine.

nice_cumulative_ns

CPU usage in nice mode since the startup of the machine.

system_cumulative_ns

CPU usage in kernel mode since the startup of the machine.

idle_cumulative_ns

CPU idle time since the startup of the machine.

iowait_cumulative_ns

CPU waiting time for I/O since the startup of the machine.

irq_cumulative_ns

Time spent on servicing interrupts.

softirq_cumulative_ns

Time spent on servicing soft interrupts.

steal_cumulative_ns

Stolen time, which is the time spent in other operating systems when running in a virtualized environment.

guest_cumulative_ns

Time spent running a virtual CPU for guest operating systems under the control of the Linux kernel.

guest_nice_cumulative_ns

Time spent running a nice guest (virtual CPU for guest operating systems under the control of the Linux kernel).

cfs_quota_ns

The amount of time in nanoseconds that the cgroup (that this SingleStore process is a member of) is allowed to spend per cfs_period_ns.

cfs_period_ns

Used in conjunction with cfs_quota_ns.

num_cpus

The number of cores on host.

timestamp_ns

The time when the data was received.

Last modified: August 29, 2022

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK