We have 3 choices:
1. Remember the compression mode at CDS dump time. At runtime, disable CDS if the compression mode is changed.
2. Same as 1, but save more than one CDS archives in the JDK image. Choose the appropriate one at start-up
3. Recompute re-compute InstanceKlass::_fields at runtime.
#1 is the simplest to implement, and will allow us to measure the benefits of using ZGC and CDS. The downside of #1 is you cannot use the same CDS image between VMs that use zgc vs g1.
If the results of #1 are promising, we can think about #2 (simpler to implement, more file footprint) and #2 (smaller file footprint, but rather complex to implement).
- duplicates
-
JDK-8240691 ClhsdbCDSJstackPrintAll incorrectly thinks CDS is in use
-
- Resolved
-
-
JDK-8232152 Enable CDS even when UseCompressedClassPointers is false
-
- Closed
-
- is cloned by
-
JDK-8232152 Enable CDS even when UseCompressedClassPointers is false
-
- Closed
-
- relates to
-
JDK-8233086 [TESTBUG] need to test field layout style difference between CDS dump time and run time
-
- Resolved
-
-
JDK-8240563 [TESTBUG] WB_IsCDSIncludedInVmBuild should support uncompressed oops/klasses
-
- Resolved
-
-
JDK-8242524 Use different default CDS archives depending on UseCompressOops
-
- Resolved
-
-
JDK-8231610 Relocate the CDS archive if it cannot be mapped to the requested address
-
- Resolved
-