harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Dmitriev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5829) [drlvm][kernel][performance] j.l.Class Serializable/Externalizable caching
Date Fri, 30 May 2008 11:37:45 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601103#action_12601103
] 

Sergey Dmitriev commented on HARMONY-5829:
------------------------------------------

Guys, let me jump in here. We have a performance degradation on SPECjvm2008:serial on r659908.
What happens if we apply the fix for this degradation to this concrete revision (659908) -
will the degradation disappear? I think this is the right way to work out the degradation.

I don't know how precise will be the approach to check the HEAD or some other revision. By
the way we have a commit now which introduces the SPECjvm2008 crash (see HARMONY-5852) so
we cannot check the HEAD.


> [drlvm][kernel][performance] j.l.Class Serializable/Externalizable caching
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-5829
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5829
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>            Reporter: Aleksey Shipilev
>            Assignee: Nathan Beyer
>             Fix For: 5.0M7
>
>         Attachments: vm-kernel-serializable-externalizable-cache-rc1.patch, vm-kernel-serializable-externalizable-cache-rc2.patch,
vm-kernel-serializable-externalizable-cache-rc3.patch, vm-kernel-serializable-externalizable-cache-V2-rc1.patch
>
>
> Serialization workloads relies on Class.isAssignableFrom(...) when looking up Serializable
and Externalizable properties (that is, implementation of interfaces). For now, DRLVM kernel
classes perform lookups on each invocation. This issue caches the mentioned properties in
Class fields and does not go to native VMClassRegistry for resolution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message