-
Enhancement
-
Resolution: Fixed
-
P4
-
1.4.1
-
1.3.1
-
b25
-
x86
-
windows_2000
Windows 2000 SP3 javac compiler performance for a Networke Mapped drive is very slow for JDK 1.3.1 and JDK 1.4.1 as compared to JDK 1.2.2
Customer moving from JDK 1.2.2 to 1.3.1 the compile time for their code has increased from 4 hours(JDK 1.2.2) to 17-18 hours(JDK 1.3.1)
A simple test case consisting of 14 ".java" files is attached (JavaTest.zip)
The following are the test results for the ".java" files in the test case on a Windows 2000 SP3 machine.using JDK 1.2.2,JDK 1.3.1and JDK 1.4.1
---------------------------------------------------
Local Network Mapped
JDK-1.2.2_013 18994ms 13092 ms
JDK1.3.1_05-b02 9864ms 19712ms
JDK1.4.1-b21 15766ms 35064ms
---------------------------------------------------
The javac -verbose output details are attached(Logging.zip)
Customer moving from JDK 1.2.2 to 1.3.1 the compile time for their code has increased from 4 hours(JDK 1.2.2) to 17-18 hours(JDK 1.3.1)
A simple test case consisting of 14 ".java" files is attached (JavaTest.zip)
The following are the test results for the ".java" files in the test case on a Windows 2000 SP3 machine.using JDK 1.2.2,JDK 1.3.1and JDK 1.4.1
---------------------------------------------------
Local Network Mapped
JDK-1.2.2_013 18994ms 13092 ms
JDK1.3.1_05-b02 9864ms 19712ms
JDK1.4.1-b21 15766ms 35064ms
---------------------------------------------------
The javac -verbose output details are attached(Logging.zip)
- relates to
-
JDK-4927845 Footprint regressions in Tiger b20
- Resolved
-
JDK-4218006 indexing rt.jar costs 400 K
- Closed
-
JDK-6614051 Javac 6.0 too slow with windows network mapped drive
- Closed
-
JDK-6186747 javac performance regression
- Resolved