-
Bug
-
Resolution: Fixed
-
P3
-
5.0
FULL PRODUCT VERSION :
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)
FULL OS VERSION :
Linux www.my2do.com 2.6.8-1.521 #1 Mon Aug 16 09:01:18 EDT 2004 i686 athlon i386 GNU/Linux
EXTRA RELEVANT SYSTEM CONFIGURATION :
Fedora core 2, Kernel 2.6.8-1
A DESCRIPTION OF THE PROBLEM :
Very high context switch rate observed under Fedora Core 2 when running any Java application (even when the applicaiton is idle, and doing nothing). Can be demonstrated by running SwingSet2 demo.
Under previous JVM (tested on 1.4.2_01 and 1.4.2_06), context switch rate (as reported by vmstat) is approx 600/per second.
Under JDK 5.0, context switch rate is approx. 1500/second .
-Xint makes no difference
-server make no difference
This makes the system very slow - even though the cpu utilization is very low ( < 5%) and there is plenty of memory (512 MB).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
In a shell window run vmstat 5, watch the cs (context switch) rate
Run any Swing application (e.g. java -jar SwingSet2.jar)
EXPECTED VERSUS ACTUAL BEHAVIOR :
Expect cs to be <600
Actual is >1500
System feels slow/unresponsive
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Run jdk1.4.2
Release Regression From : 1.4.2
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.
###@###.### 2004-11-09 23:32:02 GMT
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)
FULL OS VERSION :
Linux www.my2do.com 2.6.8-1.521 #1 Mon Aug 16 09:01:18 EDT 2004 i686 athlon i386 GNU/Linux
EXTRA RELEVANT SYSTEM CONFIGURATION :
Fedora core 2, Kernel 2.6.8-1
A DESCRIPTION OF THE PROBLEM :
Very high context switch rate observed under Fedora Core 2 when running any Java application (even when the applicaiton is idle, and doing nothing). Can be demonstrated by running SwingSet2 demo.
Under previous JVM (tested on 1.4.2_01 and 1.4.2_06), context switch rate (as reported by vmstat) is approx 600/per second.
Under JDK 5.0, context switch rate is approx. 1500/second .
-Xint makes no difference
-server make no difference
This makes the system very slow - even though the cpu utilization is very low ( < 5%) and there is plenty of memory (512 MB).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
In a shell window run vmstat 5, watch the cs (context switch) rate
Run any Swing application (e.g. java -jar SwingSet2.jar)
EXPECTED VERSUS ACTUAL BEHAVIOR :
Expect cs to be <600
Actual is >1500
System feels slow/unresponsive
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Run jdk1.4.2
Release Regression From : 1.4.2
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.
###@###.### 2004-11-09 23:32:02 GMT