Sign inTry Free

SingleStore Studio Workload Monitoring

On this page

Important

Studio is designed to work with MemSQL 6.5 or later and is only supported on Chrome and Firefox browsers at this time.

The Studio Workload Monitoring page is a feature of Studio that allows customers to record and visually analyze workload profiles at either the query or node level.

The Workload Monitoring page is built on top of the native Workload Profiling capabilities of MemSQL. As such, you should read the entire Workload Profiling topic before using Workload Monitoring in Studio.

Creating a Recording

To begin, you must create a recording of your cluster activities by clicking the Begin Profiling button in the UI. When you start recording a profile in Studio, a snapshot of INFORMATION_SCHEMA.MV_ACTIVITIES_EXTENDED_CUMULATIVE is captured. When you stop recording, another snapshot of the same table is captured and Studio calculates the difference between the two snapshots.

Analyzing a Recording

Studio allows you to analyze the resource usage of all the queries that were running in the cluster while the recording was taking place. For each query, you can inspect various metrics such as disk usage, network usage, and time spent on various things (waiting for disk I/O, waiting for CPU, etc.).

Moreover, Studio also allows you to analyze the resource usage per SingleStore node (instead of per query). This is useful to see whether a specific SingleStore node is the bottleneck of a query’s performance.

Exporting and importing workload profiles

If you want to share a recording with other Studio users, you can export a recording as a JSON file using the button in the upper-right corner of the page. Other users can then import these files through the Workload Monitoring page.

How does the Time Spent column work?

The Time Spent column on the Workload Monitoring page shows where a given query spent its time, as an average percentage of wall-clock execution time across all executions during the recording period. If advanced counters are not turned on, then this column will not yield the most precise results.

Last modified: January 10, 2023

Was this article helpful?

On this page

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