You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:38:56 UTC
[jira] [Updated] (HADOOP-10694) Remove synchronized input streams
from Writable deserialization
[ https://issues.apache.org/jira/browse/HADOOP-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-10694:
--------------------------------------
Labels: BB2015-05-TBR (was: )
> Remove synchronized input streams from Writable deserialization
> ---------------------------------------------------------------
>
> Key: HADOOP-10694
> URL: https://issues.apache.org/jira/browse/HADOOP-10694
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Gopal V
> Assignee: Gopal V
> Labels: BB2015-05-TBR
> Attachments: HADOOP-10694.1.patch, writable-read-sync.png
>
>
> Writable deserialization is slowing down due to a synchronized block within DataInputBuffer$Buffer.
> ByteArrayInputStream::read() is synchronized and this shows up as a slow uncontested lock.
> Hive ships with its own faster thread-unsafe version with hive.common.io.NonSyncByteArrayInputStream.
> !writable-read-sync.png!
> The DataInputBuffer and Writable deserialization should not require a lock per readInt()/read().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)