1. Identifying Expensive Queries

In Studio, navigate to the Workload Monitoring page.

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.

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

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.

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

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?

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.

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.