# \[AIAS-02] Architecture overview

The following picture represents the high-level architecture of how Akamas operates in this scenario.

<figure><img src="/files/DjdcrYc5qZXWFeNFoQKH" alt=""><figcaption></figcaption></figure>

The optimization goal is to make Renaissance run faster, a common optimization goal for Java applications.

Therefore, the optimization study needs to have the following properties:

* The goal of the optimization will be to minimize the response time of the Java application (another goal would be to reduce the JVM memory usage)
* The parameters to be optimized include some common JVM options, like the heap size and the garbage collector type
* The metrics that you will measure for each experiment will be the application response time, CPU, and memory usage
* The study will execute up to 30 experiments, for the duration of about 1 hour


---

# Agent Instructions: 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:

```
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-architecture-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.