hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18542) [HLC] Performance microbenchmarks
Date Wed, 23 Aug 2017 22:41:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139273#comment-16139273
] 

Enis Soztutar commented on HBASE-18542:
---------------------------------------

Any plan to use JMH for this? It seems more appropriate. You can take a look at the examples
here: https://issues.apache.org/jira/browse/HBASE-15161?focusedCommentId=15239215&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15239215

> [HLC] Performance microbenchmarks
> ---------------------------------
>
>                 Key: HBASE-18542
>                 URL: https://issues.apache.org/jira/browse/HBASE-18542
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Appy
>            Assignee: Amit Patel
>         Attachments: HBASE-18542.HBASE-14070.HLC.001.patch
>
>
> 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)

Mime
View raw message