Skip to content

Conversation

h3110n3rv3
Copy link
Contributor

The changes reflect the feature request #20644.

Adding segment categories for RAMCLass fragments:
sub4G
Frequently accessed
Infrequently accessed

Closes: #20644

@h3110n3rv3 h3110n3rv3 force-pushed the ramclass-segment-allocation branch 2 times, most recently from 65fe530 to 36f0af6 Compare June 5, 2025 21:00
The changes reflect the feature request eclipse-openj9#20644.

Adding segment categories for RAMCLass fragments:
sub4G
Frequently accessed
Infrequently accessed

Closes: eclipse-openj9#20644
Signed-off-by: Nick Kamal <nick.kamal@ibm.com>
@h3110n3rv3 h3110n3rv3 force-pushed the ramclass-segment-allocation branch from dcf14dd to b9520a6 Compare June 5, 2025 23:49
@h3110n3rv3
Copy link
Contributor Author

h3110n3rv3 commented Jun 6, 2025

The current implementation has almost the same footprint as master for lost perfPing testing. All tests passing
master_javacore.txt
ramclass_changes_javacore.txt

TODO:

  1. JIT performance testing
  2. Part 2 - figure out what fragments go in which segment

@h3110n3rv3
Copy link
Contributor Author

@TobiAjila @theresa-m for review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RamClass: Segment allocation enhancements
1 participant