You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Aleksey Shipilev (JIRA)" <ji...@apache.org> on 2007/09/18 19:03:44 UTC
[jira] Updated: (HARMONY-4815) [classlib][nio] Charset
encoding/decoding is ineffective
[ https://issues.apache.org/jira/browse/HARMONY-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Shipilev updated HARMONY-4815:
--------------------------------------
Attachment: CharsetTest.java
The test.
> [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.