Sign inTry Free

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_CPULIST

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

To get the breakdown per host, aggregate the values for each core grouped by host.

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

cpu_id

The ID of the core.

total_used_cumulative_ns

Per core CPU usage since the startup of the machine.

user_used_cumulative_ns

Per core CPU usage, in user mode, since the startup of the machine.

nice_cumulative_ns

Per core CPU usage, in nice mode, since the startup of the machine.

system_cumulative_ns

Per core CPU usage, in kernel mode, since the startup of the machine.

idle_cumulative_ns

Per core CPU idle time since the startup of the machine.

iowait_cumulative_ns

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

irq_cumulative_ns

Time spent on servicing interrupts on the core.

softirq_cumulative_ns

Time spent on servicing soft interrupts on the core.

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).

timestamp_ns

The time when the data was received.

Last modified:

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In