-
Enhancement
-
Resolution: Fixed
-
P4
-
8-shenandoah, 11-shenandoah, 12, 13
-
b05
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8219085 | 12.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
Current Shenandoah control thread runs with the default priority (NearMaxPriority):
ShenandoahControlThread::ShenandoahControlThread():
create_and_start();
ConcurrentGCThread:
// Create and start the thread (setting it's priority.)
void create_and_start(ThreadPriority prio = NearMaxPriority);
CMS and others are able to use critical thread priority, for example:
create_and_start(UseCriticalCMSThreadPriority ? CriticalPriority : NearMaxPriority);
We should consider doing the same for Shenandoah.
ShenandoahControlThread::ShenandoahControlThread():
create_and_start();
ConcurrentGCThread:
// Create and start the thread (setting it's priority.)
void create_and_start(ThreadPriority prio = NearMaxPriority);
CMS and others are able to use critical thread priority, for example:
create_and_start(UseCriticalCMSThreadPriority ? CriticalPriority : NearMaxPriority);
We should consider doing the same for Shenandoah.
- backported by
-
JDK-8219085 Shenandoah control thread should be able to run at critical priority
- Resolved
- is blocked by
-
JDK-8217378 UseCriticalCMSThreadPriority is broken
- Resolved