-
Bug
-
Resolution: Duplicate
-
P4
-
16, 17, 18
All GCs (Serial, Parallel, G1, Shenandoah, Z) are effected; 15-20% regression for different GCs.
```
java -Xms4g -Xmx4g -jar dacapo-9.12-MR1-bach.jar h2 -s huge -t 1 -n 1
```
Example of output using G1:
Before
===== DaCapo 9.12-MR1 h2 PASSED in 124958 msec =====
After
===== DaCapo 9.12-MR1 h2 PASSED in 151726 msec =====
So far the regression is observed only on Intel, but not on AMD.
More testing shows that this regression is only for single thread. If I use more threads (e.g. -t 2), the regression seems to go away.
```
java -Xms4g -Xmx4g -jar dacapo-9.12-MR1-bach.jar h2 -s huge -t 1 -n 1
```
Example of output using G1:
Before
===== DaCapo 9.12-MR1 h2 PASSED in 124958 msec =====
After
===== DaCapo 9.12-MR1 h2 PASSED in 151726 msec =====
So far the regression is observed only on Intel, but not on AMD.
More testing shows that this regression is only for single thread. If I use more threads (e.g. -t 2), the regression seems to go away.
- duplicates
-
JDK-8257975 Regression ~ 2.5% in SwingMark.Table after JDK-8253064
- Closed
-
JDK-8277180 Intrinsify recursive ObjectMonitor locking for C2 x64 and A64
- Resolved
-
JDK-8281043 Intrinsify recursive ObjectMonitor locking for PPC64
- Resolved
- relates to
-
JDK-8273107 RunThese24H times out with "java.lang.management.ThreadInfo.getLockName()" is null
- Resolved
-
JDK-8253064 monitor list simplifications and getting rid of TSM
- Resolved