[
https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404429#comment-16404429
]
Yu Li commented on HBASE-20188:
-------------------------------
Thanks for the additional details sir [~anoop.hbase] [~ram_krish], but please
allow me to get back to the problem mentioned in description:
bq. There is rumor that it is much slower, that the problem is the asyncwal
writing. Does in-memory compaction slow us down or speed us up? What happens
when you enable offheaping?
I don't like rumors (smile). So I won't disturb the discussion on detailed
issues here (if I already have, please forgive me) but rather carry on some
perf-comparison and see with my own eyes, will share the observation also of
course.
> [TESTING] Performance
> ---------------------
>
> Key: HBASE-20188
> URL: https://issues.apache.org/jira/browse/HBASE-20188
> Project: HBase
> Issue Type: Umbrella
> Components: Performance
> Reporter: stack
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: flamegraph-1072.1.svg, flamegraph-1072.2.svg, tree.txt
>
>
> How does 2.0.0 compare to old versions? Is it faster, slower? There is rumor
> that it is much slower, that the problem is the asyncwal writing. Does
> in-memory compaction slow us down or speed us up? What happens when you
> enable offheaping?
> Keep notes here in this umbrella issue. Need to be able to say something
> about perf when 2.0.0 ships.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
