Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Analyze possible improvements for startup time and after-start memory footprint #23730

@mabartos

Description

@mabartos

Description

Recently, we've faced certain performance drops for startup time and after-start memory footprint after Quarkus 3 upgrade. We are not able to continuously compare the performance measures with additional improvements, so an additional analysis of performance is needed.

The outcome of this issue:

  • Analyze major performance gaps found in Keycloak
  • Propose proper solutions for resolving them
  • Aggregate the findings into a single central point (this epic) in order to properly trace them

More details in #20448

Sub-issues

Metadata

Metadata

Assignees

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions