-
Bug
-
Resolution: Fixed
-
P1
-
5.0u7
-
b01
-
generic
-
generic
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2137119 | 6 | William Harnois | P3 | Closed | Fixed | b85 |
JDK-2135229 | 1.4.2_13 | Abhijit Saha | P3 | Closed | Fixed | b01 |
We are currently using RTpatch software to build the binary difference between a update release (5.0uX) and it's baseline release (5.0). By default, RTPatch will use it's software to compress the binary diff, and then our installer will use lzx compression to compress further. However, there is no reason to have 2 separate compressors.
By using the NOCOMPRESS rtpatch flag, we can turn the rtpatch compression off, and only use our lzx compression. This will reduce the download of all JRE full installs as well as updates by 264KB. Also, because there is only 1 uncompression, it will make our installers somewhat faster (I haven't done any benchmarks on this yet).
The saving should be relatively bigger for the JDK installer also.
By using the NOCOMPRESS rtpatch flag, we can turn the rtpatch compression off, and only use our lzx compression. This will reduce the download of all JRE full installs as well as updates by 264KB. Also, because there is only 1 uncompression, it will make our installers somewhat faster (I haven't done any benchmarks on this yet).
The saving should be relatively bigger for the JDK installer also.
- backported by
-
JDK-2135229 using rtpatch flag NOCOMPRESS will reduce each JRE download by 264KB
- Closed
-
JDK-2137119 using rtpatch flag NOCOMPRESS will reduce each JRE download by 264KB
- Closed
- relates to
-
JDK-6388857 JRE installation process slowed down by average of 5 seconds
- Closed