Remove native image #6847
Merged
Remove native image #6847
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
snazy
force-pushed
the
remove-native-image
branch
from
8bae811
to
ed1cb0b
Compare
dimas-b
previously approved these changes
May 17, 2023
snazy
force-pushed
the
remove-native-image
branch
2 times, most recently
from
412edd4
to
c7b7406
Compare
snazy
force-pushed
the
remove-native-image
branch
from
c7b7406
to
367baac
Compare
|
|
adutra
approved these changes
May 19, 2023
snazy
added a commit
to snazy/nessie
that referenced
this pull request
May 24, 2023
snazy
added a commit
that referenced
this pull request
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The native image isn't used in the wild (10 total pulls for 0.58.0+0.58.1 vs ~500 for the Java image).
There are already issues w/ native images. Spanner + BigTable (effectively all Google services) don't work in native images due to code issues in Google code. Also there are "strange" native-test issues in the Quarkus 3 PR.
FaaS (lambda) style deployments do not really need native images. Sure, the startup is faster, but those instances cannot run for long, because SerialGC can easily cause STWs of many seconds. So keeping FaaS instances up longer (and maybe have a "spare one") should mitigate that issue.
Also, we can only build x86_64/Linux native images.