> For the complete documentation index, see [llms.txt](https://docs.akamas.io/quick-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-sandbox/aias-02-guide-create-a-study-to-optimize-java-performance-using-the-akamas-ui/aias-02-define-the-performance-metrics.md).

# \[AIAS-02] Define the performance metrics

Now, you can select the metrics of interest among all the metrics provided by your components.

You can do that by expanding the **Choose metrics** section and selecting the three metrics of the `renaissance` component:

* CPU used, representing the total CPU used by the JVM process running the benchmark
* Memory used, representing the peak memory used by the JVM process running the benchmark
* Response time, representing the response time of the benchmark

You can also click on the `jvm` component to deselect its corresponding metrics, as they are not available in this example.

<figure><img src="/files/Zl6aqRoXCDEsy2NObqbi" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-sandbox/aias-02-guide-create-a-study-to-optimize-java-performance-using-the-akamas-ui/aias-02-define-the-performance-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.