4. Are key resources being overused?

On this page

The next step in troubleshooting your cluster is looking at key resources to see if they are being overused.

For a quick sanity check, navigate to the Studio Dashboard to look at resource usage against their respective totals available by hovering over each.
Check the Studio Hosts and/or Nodes pages to look at CPU and memory usage.
Sort on CPU Usage, Memory Usage, and Disk Usage. Are there resources being overused?
If you see one or more resources approaching their limit (e.g., memory, disk, or CPU limits), consider the following:
- Have you added a new workload to your cluster that is using more resources?
- Have you loaded more data (on disk, or in memory)?
- Have you increased concurrency?
- Does your workload require more nodes to meet the scale?
- Is there an expensive workload or query that is causing a spike and could be optimized?

Next Steps

If you identify one or more key resources being overused: return to Step 1, to identify whether there are specific queries causing this.
If the cause is not specific queries, or there are no resource usage issues: continue to Step 5.

Last modified: September 10, 2024

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.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
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.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

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