> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/reporting/performance-improvements-for-report-creation.md).

# Performance Improvements for Report Creation

Discover desktop client reporting performance boosts. Learn optimized techniques to create reports faster and enhance data handling for efficient workflows.

In order to improve performance of report creation, it is important to understand the difference between server-side filtering and report-side filtering. Server-side filtering is done when a user starts to generate a report. The window below shows where a user can set filters (\[Assigned to] equals Me). This is done on the server before data is sent to the client (or the report, respectively). It allows you to decrease the amount of data sent to the report.  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_performance_improvements_for_report_creation_custom.png" alt=""><figcaption></figcaption></figure>

Report-side filtering is set up in the report itself, i.e. the data sent by the server to a user’s client machine can be filtered additionally inside the report. A general rule of thumb for improving report performance is to set up a server-side filter so that only data that is really needed in the report is sent to the report (too much data slows down the report).

That is why a user can also configure the data sent to the report in general (it is an additional point for improvement) in more detail. A typical example is to exclude pictures if they are not shown/used in the report.&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_performance_improvements_for_report_creation_custom_2.png" alt=""><figcaption></figcaption></figure>

&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_performance_improvements_for_report_creation_custom_3.png" alt=""><figcaption></figcaption></figure>

&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_performance_improvements_for_report_creation_custom_4.png" alt=""><figcaption></figcaption></figure>


---

# 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.aqua-cloud.io/documentation/desktop-client/reporting/performance-improvements-for-report-creation.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.