> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/compare-workloads.md).

# Compare two workloads

Compare workloads across time periods, instances, or applications.

Compare workloads across time periods, instances, or applications to surface differences, trends, and regressions.

**Example prompts:**

* **Between periods:**
  * "Compare prod-eu-1 today 08:00-10:00 vs yesterday same window: did it regress?"
* **Between instances:**
  * "Compare workload between prod-eu-2 and prod-eu-1 and explain the differences."
* **Between applications, datacenters, or environments:**
  * "Compare the zabbix cohort vs the crm cohort since 08:00."
  * "Which datacenter carries the most load this morning, dc1 or dc10?"

{% @arcade/embed url="<https://app.arcade.software/share/GuW4SppISkrkthIpWTOG>" flowId="GuW4SppISkrkthIpWTOG" %}

*This walkthrough was recorded with the Claude Desktop app.*

{% hint style="info" %}
**Continue from the menu.** A comparison ends with a short menu of next steps: drill into the query that diverges the most between the two sides, run a full workload analysis on the heavier one, or explore the lock or I/O pressure behind the difference. Pick an option to keep the investigation going without retyping the context.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datasentinel.io/manual/ai-connector/analyze-and-tune-workloads/compare-workloads.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.