harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Shipilev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5829) [drlvm][kernel][performance] j.l.Class Serializable/Externalizable caching
Date Mon, 19 May 2008 08:34:55 GMT

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

Aleksey Shipilev commented on HARMONY-5829:
-------------------------------------------

Nathan, the synchronization is not needed here. In case of several threads concurrently requesting
these properties and then caching the values in corresponding fields, the field values would
not depend on order of execution, e.g. there is no race condition in this code. Caching of
non-changeable data is free.

> [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: Pavel Pervov
>         Attachments: vm-kernel-serializable-externalizable-cache-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