[ https://issues.apache.org/jira/browse/HBASE-18686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Patel updated HBASE-18686: ------------------------------- Description: Based on [performance benchmarks on the clocks|https://issues.apache.org/jira/browse/HBASE-18542?focusedCommentId=16141932&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16141932], the Clock#now and Clock#update methods of the HLC implementation are costly in multithreaded scenarios especially due to synchronization around the entire methods. Thus we need an improved implementation of Clock#now and Clock#update such that it would perform better in the presence of multiple threads. (was: Based on [performance benchmarks on the clocks|https://issues.apache.org/jira/browse/HBASE-18542?focusedCommentId=16141932&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16141932], the Clock#now and Clock#update methods of the HLC implementation are costly in multithreaded scenarios especially due to synchronization around the entire methods.) > Improve HLC implementation performance > -------------------------------------- > > Key: HBASE-18686 > URL: https://issues.apache.org/jira/browse/HBASE-18686 > Project: HBase > Issue Type: Sub-task > Reporter: Amit Patel > Priority: Critical > > Based on [performance benchmarks on the > clocks|https://issues.apache.org/jira/browse/HBASE-18542?focusedCommentId=16141932&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16141932], > the Clock#now and Clock#update methods of the HLC implementation are costly > in multithreaded scenarios especially due to synchronization around the > entire methods. Thus we need an improved implementation of Clock#now and > Clock#update such that it would perform better in the presence of multiple > threads. -- This message was sent by Atlassian JIRA (v6.4.14#64029)