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-5633) [drlvm][performance] ObjectStreamClass lookup improvement
Date Sun, 23 Mar 2008 20:07:24 GMT

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

Nathan Beyer commented on HARMONY-5633:
---------------------------------------

Can you elaborate on the "Breaks specification" pitfall? I'm not exactly clear on what you
mean by this.

I'm not familiar with the MT/SerialBench, can you provide a link or some more information
about this?

> [drlvm][performance] ObjectStreamClass lookup improvement
> ---------------------------------------------------------
>
>                 Key: HARMONY-5633
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5633
>             Project: Harmony
>          Issue Type: Improvement
>            Reporter: Aleksey Shipilev
>         Attachments: 0001-serial-lookupClass.patch
>
>
> For now, ObjectStreamClass (OSC) is created on-the-fly during serialization/deserialization
and stored in static cache.
> Performance problems arose when several threads doing the lookups, hitting on synchronized
cache. Moreover, the cache is built around WeakHashMap to ensure GC of OSCs. This issue is
the source of scalability problems for multi-threaded serialization benchmarks.

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