[AIAB-01] Explore the results

You can now look at the results of your first AI-driven performance optimization study.

Notice: in your environment, you might achieve different results with respect to what is described in this guide. The actual best configuration might depend on your actual setup - operating systems, cloud or virtualization platform, and the hardware

Application response time cut by 40%

Select your study from the UI Study menu.

The Summary tab displays high-level study information at a glance, including the best score obtained so far, a summary of the optimized parameters, and their values for the best configuration.

By optimally configuring the JVM parameters, Akamas was able to cut the application response time by almost 41%:

The automatic optimization took about 1 hour

The Analysis tab shows the experiments' score over time.

Properly tuning a modern JVM is a complex challenge, and might require weeks of time and effort even for performance experts.

Akamas AI is designed to converge rapidly toward optimal configurations. In this case, Akamas was able to find the optimal JVM configuration after only 30 automated performance experiments:

Below the optimization chart, you can also find a table showing aggregated performance metrics and parameters set for each experiment. For each metric, you can find a percentage variation with respect to the baseline experiment, so that you can quickly see the impact the new parameters had on other interesting key metrics (you can sort them too).

Besides reducing response time, Akamas also made the application more CPU efficient

The Insights drawer lets you explore the additional benefits of the configurations Akamas explored with respect to other key metrics besides the goal. Choose some KPIs in the study's main page to discover the insights.

In this optimization, the best configurations Akamas found not only made the application run significantly faster, but also made the application run more efficiently on the CPU:

From a CPU efficiency perspective, the best configuration Akamas found was able to cut CPU utilization by 33%, while still improving response time by 17%.

How did Akamas achieve that? A look at the best configurations

What are the best JVM settings Akamas found that made the application run so much faster?

You can find them in the Best Configuration table in the Summary tab.

Without being told anything about how the application works, Akamas learned the best settings for some interesting JVM parameters:

• the max heap size was slightly changed

• the best garbage collector is Parallel

Those are not easy insights to discover, without being an expert and doing dozens of manual performance experiments!

A look at the performance over time metrics

The Metrics tab allows you to check the metrics that the telemetry modules collected over time for each experiment. In the chart, Akamas presents you with a comparison of the key metrics related to the baseline and the best experiment (you can add more using the filters).

Despite this first optimization relying on short benchmark execution times, the best configuration is consistently faster than the baseline.

Congratulations! You have just completed your first Akamas optimization of a sample Java application!