-
Notifications
You must be signed in to change notification settings - Fork 722
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
Send cached J9ROMClass hashes to JITServer #19847
Conversation
Attn @mpirvu. |
d4c85fb
to
70996e3
Compare
70996e3
to
6f7cfc7
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
jenkins test sanity xlinuxjit,zlinuxjit,alinux64jit jdk21 |
On arm and zlinux JITServer tests show: xlinux tests have not finished yet |
If a JITServer client has a cached hash for a ROMClass, it may now send this hash to the server to avoid the server having to re-hash (and possibly re-pack) the ROMClass received from the client. The server will store this cached hash in its shared ROMClass cache. Currently, only the stored hashes of generated classes are sent to the server. Signed-off-by: Christian Despres <despresc@ibm.com>
6f7cfc7
to
3a50aeb
Compare
When I changed |
jenkins test sanity xlinuxjit,zlinuxjit,alinux64jit jdk21 |
jenkins test sanity xlinuxjit jdk21 |
If a JITServer client has a cached hash for a ROMClass, it may now send this hash to the server to avoid the server having to re-hash (and possibly re-pack) the ROMClass received from the client. The server will store this cached hash in its shared ROMClass cache. Currently, only the stored hashes of generated classes are sent to the server.