harmony-commits mailing list archives

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

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

Nathan Beyer commented on HARMONY-5829:

I don't think it's overkill, I think it's correct. After reviewing the memory model, I believe
the fields needs to be volatile, at least 'resolvedProperties' field and use the appropriate
access paradigms for volatile fields [1].

[1] http://www.ibm.com/developerworks/java/library/j-jtp06197.html#2.0

> [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, vm-kernel-serializable-externalizable-cache-rc2.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.

View raw message