[ https://issues.apache.org/jira/browse/HADOOP-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540513#comment-16540513 ]
Prasanth Jayachandran commented on HADOOP-15598: ------------------------------------------------ [~ste...@apache.org] Yeah. There will definitely be more places for this optimization. I did not look anything beyond checksum bottleneck. Is it ok to handle the wider optimization in a follow-up? > 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, 3.1.1 > Reporter: Prasanth Jayachandran > Assignee: 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org