harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Shipilev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4815) [classlib][nio] Charset encoding/decoding is ineffective
Date Tue, 18 Sep 2007 17:25:44 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528457
] 

Aleksey Shipilev commented on HARMONY-4815:
-------------------------------------------

Throwing away unpatched version and stressing best versions:

Sun 1.6.0 (-server -Xmx512m -Xms512m):
 1 thread - 11079
 2 threads - 7170
 4 threads - 3883
 8 threads - 1900
 16 threads - 1682
 32 threads - 1743
 64 threads - 1738

Harmony-r576670-patched (-Xem:server -Xms512m -Xmx512m):
 1 thread - 23465
 2 threads - 12003
 4 threads - 7082
 8 threads - 3500
 16 threads - 4312
 32 threads - 4553
 64 threads - 4317

Still, 2.5x times slower, but scales extremely well.

> [classlib][nio] Charset encoding/decoding is ineffective
> --------------------------------------------------------
>
>                 Key: HARMONY-4815
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4815
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Aleksey Shipilev
>         Attachments: CharsetTest.java, HARMONY-4815.patch
>
>
> Excess synchronizations and caching of encoder/decoder causes stalls if many thread doing
encoding/decoding simultaneously. As far as one single instance of Encoder/Decoder is not
thread-safe, we could create the separate encoder/decoder each time it is demanded. The overhead
will be caused for excess object allocations, but boost from eliminating serial code is much
bigger.

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