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

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12597362#action_12597362 ] 

Pavel Pervov commented on HARMONY-5829:
---------------------------------------

Aleksey, Is it better to move this caching to class creation/preparation in native?

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