harmony-commits mailing list archives

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

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

Alexey Varlamov commented on HARMONY-5829:
------------------------------------------

Re bootstrap phase, there is already special handling of primordial classes, I believe it
should be enough. During that phase, invoking constructors can be deffered or replaced with
direct field assignments.
Anyway, I suggested to use Java constructor mainly for consistency and clarity; if it is too
tricky or troublesome - just skip this idea

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


Mime
View raw message