Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63521 - Please provide OpenJDK 8, built with Shenandoah

Attached to Project: Community Packages
Opened by Alexander (AlexanderR) - Wednesday, 21 August 2019, 23:18 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 21 August 2019, 23:42 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Shenandoah is a modern low-pause garbage collector for Java, created and maintained by Red Hat. From my experience, Shenandoah tremendously reduces GC pauses — running IntelliJ Idea with Shenandoah completely eliminated all UI hiccups on my PCs. Unfortunately, upstream OpenJDK does not include Shenandoah until JDK 12 (and even Oracle's OpenJDK 12 does not enable it by default). Instead Oracle has created their own low-latency garbage collector (ZGC). ZGC is also very good, but it is only available since OpenJDK 11.

A lot of software, including Android Studio, does not support Java versions after Java 8, but would benefit a lot from a low-latency garbage collector. Red Hat build of JDK 8 includes support for Shenandoah. It is also available from https://builds.shipilev.net/ (Shipilev is former Oracle employee, currently working at Red Hat). I'd like Arch repositories to include Shenandoah-enabled JDK as well.

Fedora package (which has Shenandoah support) may be useful as guideline: https://src.fedoraproject.org/rpms/java-1.8.0-openjdk
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Wednesday, 21 August 2019, 23:42 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Major new features of a software stack should be enabled by updating to major new versions of the software stack. We are going to continue to build java as upstream delivers it.

Android Studio should stop living in the past. Yes, I know how unlikely it is you can do anything about that. But that fact does not change anything.

Loading...