# 1. Identifying Expensive Queries

1. In Studio, navigate to the [Workload Monitoring](https://docs.singlestore.com/db/v9.1/reference/singlestore-tools-reference/singlestore-studio/singlestore-studio-workload-monitoring.md) page.

2. If you do not have monitoring data from SingleStore’s [monitoring solution](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/cluster-health-and-performance/configure-monitoring.md), 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.](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt2336da4b316bf194/6a2c26aea36d0ac0a4b81e1e/16083b5794f43e-LxY0l3.png)

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](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/2-investigating-expensive-queries.md).
* If you have not identified any useful information, skip to [Step 3](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/3-are-any-queries-waiting-on-something.md).

***

Modified at: June 11, 2026

Source: [/db/v9.1/user-and-cluster-administration/troubleshooting/1-identifying-expensive-queries/](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/1-identifying-expensive-queries/)

(An index of the documentation is available at /llms.txt)