| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2183203 | 7 | Tony Printezis | P3 | Closed | Fixed | b72 |
| JDK-2189990 | 6u21 | Tony Printezis | P3 | Resolved | Fixed | b01 |
| JDK-2182819 | 6u18 | Tony Printezis | P3 | Resolved | Fixed | b02 |
| JDK-2182629 | hs16 | Tony Printezis | P3 | Resolved | Fixed | b09 |
Using the same region size for small 32-bit JVMs, as well as large 64-bit JVMs, might not be appropriate. We should at least set the region size depending on the build (say: smaller for 32-bit client, small for 32-bit server, and larger for 64-bit server, for some definition of smaller, small, and larger). Ideally, we should experiment with how expensive it is to replace the region size constant with a variable which can either be set ergonomically (depending on heap size), as well as be user-settable.
- backported by
-
JDK-2182629 G1: use larger and/or user settable region size
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-6819061 G1: eliminate serial Other times that are proportional to the collection set length
-
- Resolved
-
-
-
- Closed
-
(1 relates to)