Sign inTry Free

1. Identifying Expensive Queries

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

On this page

  1. In Studio, navigate to the Workload Monitoring page.

  2. If you do not have monitoring data from SingleStore’s monitoring solution, select Begin Profiling to capture current cluster activity for a period of time. Be sure to record during the workload or query of interest, if one has been identified while collecting data in the previous step.

  3. If one has been identified, switch the database selector to the suspect database.

    All active activities are listed with name, activity category, database, elapsed time, and more in the Workload Monitoring page.

  4. Sort on Elapsed Time and Run Count by selecting the field name. Hover over the Time Spent bar and review which queries are consuming the most amount of time.

  5. Sort on CPU, Memory, and Network to identify other resource-intensive queries.

  6. Distinguish query shapes that may be resource-intensive due to having a high run count compared to others. For example, is a query using resources because of how many times it has been run, or is it using a large amount of resources across a low number of runs?

  7. Note the activity_name of queries that have high elapsed time, run count, and/or that are using a large amount of a given resource.

  8. Select the Nodes tab to identify which node these queries are running. The Nodes tab can also help to confirm why a specific node is running slowly.

Next Steps

  • If you have identified a long-running query that is using a large amount of resources or has an unusual run count, continue to Step 2.

  • If you have not identified any useful information, skip to Step 3.

Last modified: November 26, 2024

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