Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

danielkec
Copy link

No description provided.

@mraible
Copy link
Contributor

mraible commented Jun 21, 2023

Thanks for your help, @danielkec! I tried these optimizations and found the startup time to be around 34 ms.

(28 + 36 + 36 + 36 + 34) / 5 = 34

When I tested Helidon last night, it was 43.8 ms.

I also tested memory:

Megabytes before request: 57 MB (was 74)
Megabytes after request: 81 MB (was 91)
Megabytes after 5 requests: 115 MB (was 124)

Helidon seems to increase the memory used 6-8 MB for each request. Is this a known issue?

Micronaut had a similar problem last year. They added the following to their default application.yml to fix it:

netty.default.allocator.max-order: 3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.