hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15598) DataChecksum calculate checksum is contented on hashtable synchronization
Date Wed, 11 Jul 2018 15:20:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540234#comment-16540234

Steve Loughran commented on HADOOP-15598:

BTW, does this affect branch-3.1 too? If so, change the affects-version field and we can plan
to commit it there too. thanks

> DataChecksum calculate checksum is contented on hashtable synchronization
> -------------------------------------------------------------------------
>                 Key: HADOOP-15598
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15598
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: common
>    Affects Versions: 3.2.0
>            Reporter: Prasanth Jayachandran
>            Priority: Minor
>         Attachments: HADOOP-15598.1.patch, HADOOP-15598.1.patch, Screen Shot 2018-07-11
at 1.45.06 AM.png, Screen Shot 2018-07-11 at 2.01.54 AM.png
> When profiling a multi-threaded hive streaming ingest, observed lock contention on java.util.Properties
getProperty() to check if os is "sparc". java.util.Properties internally uses HashTable. HashTable.get()
is synchronized method. In the test application, on a 30s profile with 64 threads ~40% CPU
time is spent on getProperty() contention. See attached snapshot.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message