ramkrishna.s.vasudevan commented on HBASE-15536:

I would generally say that pls do not consider the profile report in terms of 
comparisons in CellComparator. It is always in the top but sometimes it tends 
to vary because
-> Not always profilers give the source of truth
-> Next is that all the comparsions are going to be same like the mutations 
added to memstore and the Scanquerymatcher that does comparsions during 
Ya may be in default case comparisoins are more because they are much faster so 
more flushes/compactions?
As I said the profile does not immediately give the hot spot. But there is 
something other than the comparators that we need to check. I will report back 
on this tomorrow after doing some more analysis.

> Make AsyncFSWAL as our default WAL
> ----------------------------------
>                 Key: HBASE-15536
>                 URL: https://issues.apache.org/jira/browse/HBASE-15536
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: HBASE-15536-v1.patch, HBASE-15536-v2.patch, 
> HBASE-15536-v3.patch, HBASE-15536-v4.patch, HBASE-15536-v5.patch, 
> HBASE-15536.patch, latesttrunk_asyncWAL_50threads_10cols.jfr, 
> latesttrunk_defaultWAL_50threads_10cols.jfr
> As it should be predicated on passing basic cluster ITBLL

This message was sent by Atlassian JIRA

Reply via email to