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

Shenandoah GC support for mandrel #279

Open
ksvasan opened this issue Aug 11, 2021 · 2 comments
Open

Shenandoah GC support for mandrel #279

ksvasan opened this issue Aug 11, 2021 · 2 comments
Labels
enhancement New feature or request not-Stale

Comments

@ksvasan
Copy link

ksvasan commented Aug 11, 2021

Is your feature request related to a problem? Please describe.
Is there a plan for adding shenandoah GC support to mandrel, asking this since it was contributed by redhat to the upstream openjdk. Having a low latency GC like shenandoah would allow for wide spread adoption on the server side and it can become a serious competitor to the likes of golang.

Describe the solution you'd like
Shenandoah GC support for graalvm native-image binaries to have a GC which can compete with golang latencies.

Describe alternatives you've considered
There is an issue in the upstream for Shenandoah support in native-image (oracle#3472)

Additional context
N/A

@ksvasan ksvasan added the enhancement New feature or request label Aug 11, 2021
@zakkak
Copy link
Collaborator

zakkak commented Aug 16, 2021

Hi @ksvasan,

Is there a plan for adding shenandoah GC support to mandrel, asking this since it was contributed by redhat to the upstream openjdk.

No, there is no plan or commitment on delivering this feature, but there is an ongoing effort from @bakaliosdim (building on top of oracle#2426) to add Shenandoah GC support to graal, which as you already pointed out is being tracked in oracle#3472.

Furthermore, it's worth noting that the current work aims to add Shenandoah GC to the Graal JIT compiler. native-image support would come as a second step and would require more work to be achieved.

@github-actions
Copy link

This issue appears to be stale because it has been open 30 days with no activity. This issue will be closed in 7 days unless Stale label is removed, a new comment is made, or not-Stale label is added.

@github-actions github-actions bot added the Stale label Sep 16, 2021
@zakkak zakkak added not-Stale and removed Stale labels Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request not-Stale
Projects
None yet
Development

No branches or pull requests

2 participants