> 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-architecture-overview.md).
# \[AIAS-02] Architecture overview
The following picture represents the high-level architecture of how Akamas operates in this scenario.
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
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.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=&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.
