Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HostnameResolver class initialization is pretty heavy #5429

Open
geoand opened this issue Dec 30, 2024 · 3 comments · May be fixed by #5439
Open

HostnameResolver class initialization is pretty heavy #5429

geoand opened this issue Dec 30, 2024 · 3 comments · May be fixed by #5439

Comments

@geoand
Copy link
Contributor

geoand commented Dec 30, 2024

This class is loaded as part of the initialization of AddressResolverOptions, but the way it tries to extract the ndots and rotate configuration is pretty heavy (and shows up in flamegrapahs for startup of a Quarkus application).

I believe it could be made to not use regular expressions and also pull all the options in a single pass, no?

@tsegismont
Copy link
Contributor

That's possible, if you'd like to contribute such an enhancement, please go ahead and send a PR (ideally with a benchmark)

@geoand
Copy link
Contributor Author

geoand commented Jan 3, 2025

I'll keep it on my radar

@geoand
Copy link
Contributor Author

geoand commented Jan 10, 2025

#5439 is what I have in mind

geoand added a commit to geoand/vert.x that referenced this issue Jan 14, 2025
geoand added a commit to geoand/vert.x that referenced this issue Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants