-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Purge JITServer caches sooner when memory is low #11189
Conversation
I will review it shortly. Please change the title to "Purge JITServer caches sooner when memory is low" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see the inline comments.
8757fa3
to
44d9425
Compare
44d9425
to
5af333d
Compare
Added variable OLD_AGE_UNDER_LOW_MEMORY to purge the Client cache at the server sooner when memory is low. If a client didn't issue a request in more than 5 mins and memory is low, its cache will be purged from the server. I also added option oldAge for OLD_AGE and TimeBetweenPurges for TIME_BETWEEN_PURGES. They can be specified using -xjit option. issue: eclipse-openj9#11161 Signed-off-by: Eman Elsabban <eman.elsaban1@gmail.com>
5af333d
to
390f344
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Could you please tests the implementation locally to make sure it works as designed? Jenkins testing won't show much in this case. Thanks
jenkins test sanity plinuxjit,xlinuxjit,zlinuxjit jdk11 |
jenkins test sanity plinuxjit,xlinuxjit jdk11 |
@EmanElsaban Tests have passed. I will merge this PR as soon as you confirm that local tests show behavior is as intended. |
I copied my jdk to acmeair benchmark and tested there. I had 2 acmeair clients connected to jitserver and I limited jitserver memory to 50MiB(low memory scenario). I started the 2 clients at the same time and I set oldAge=3000 , timeBetweenPurges=100 , oldAgeUnderLowMemory=500 . In the vlog for server I see the 500 value set and the data being purged(the purging is triggered):
I also tested using |
I am merging this PR since all tests (Jenkins and local) have passed. |
Added variable OLD_AGE_UNDER_LOW_MEMORY to purge the Client cache at the server sooner
when memory is low. If a client didn't issue a request in more than 5 mins and memory is low, its
caches will be purged from the server.
issue: #11161
Signed-off-by: Eman Elsabban eman.elsaban1@gmail.com