[
https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404406#comment-16404406
]
ramkrishna.s.vasudevan commented on HBASE-20188:
------------------------------------------------
With this load, lets try with Default memstore also to see what happens? And
then with CMS try tuning diff configs?
If having CMS makes the actual flush to cost more because of compares but at
the same time since CMS creates smaller size CSLM writes are faster, may be
should have the right balance there?
bq.Is the Eshcar's fix to HBASE-18294 included?
I think this should be there if am not wrong.
> [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)
