[jira] [Updated] (HBASE-18542) [HLC] Performance microbenchmarks

["Appy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-18542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Appy updated HBASE-18542:
-------------------------
    Description: 
Need tests to benchmark performance of Clock#now() and update() functions (for all types of clocks).
If update() is too costly, we can do optimizations in ExecuteProceduresRemoteCall#call(), HRegion#replayRecoveredEdits() and other places where we call update() in loop. Instead, it might be faster to calculate max timestamp in loop and call update() just once.

  was:
Need tests to benchmark performance of Clock#now() and update() functions (for all types of clocks).
If update() is too costly, we can do optimizations in ExecuteProceduresRemoteCall#call() and other places where we call update() in loop. Instead, it might be faster to calculate max timestamp in loop and call update() just once.


> [HLC] Performance microbenchmarks
> ---------------------------------
>
>                 Key: HBASE-18542
>                 URL: https://issues.apache.org/jira/browse/HBASE-18542
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Appy
>
> Need tests to benchmark performance of Clock#now() and update() functions (for all types of clocks).
> If update() is too costly, we can do optimizations in ExecuteProceduresRemoteCall#call(), HRegion#replayRecoveredEdits() and other places where we call update() in loop. Instead, it might be faster to calculate max timestamp in loop and call update() just once.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)