You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Nathan Beyer (JIRA)" <ji...@apache.org> on 2008/05/25 06:17:55 UTC

[jira] Resolved: (HARMONY-5829) [drlvm][kernel][performance] j.l.Class Serializable/Externalizable caching

     [ https://issues.apache.org/jira/browse/HARMONY-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Beyer resolved HARMONY-5829.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0M7

I've applied a modified version of the third patch at r659908 and r659909. Please verify that it was applied as expected.

> [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
>
>
> 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.