[
https://issues.apache.org/jira/browse/HBASE-9775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816067#comment-13816067
]
stack commented on HBASE-9775:
------------------------------
bq. I confirm. That's by design (in YCSB, and in a way, in HBase as well, 0.94
included...). It does not really match a real use case, an application server
would have a single connection.
It is a little odd. We are 'constraining' all to go via the one connection.
Even if you up the threads because you want more throughput, we will constrain
you to run over the one connection. Let me try and see if connection per
thread makes a difference.
bq. IIRC, I forgot to change hbase-site.xml, so the default has not changed at
the end .
You fixing boss? Apparently [~eclark] made the change in this test anyways?
> Client write path perf issues
> -----------------------------
>
> Key: HBASE-9775
> URL: https://issues.apache.org/jira/browse/HBASE-9775
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.96.0
> Reporter: Elliott Clark
> Priority: Critical
> Attachments: 9775.rig.txt, 9775.rig.v2.patch, 9775.rig.v3.patch,
> Charts Search Cloudera Manager - ITBLL.png, Charts Search Cloudera
> Manager.png, hbase-9775.patch, job_run.log, short_ycsb.png, ycsb.png,
> ycsb_insert_94_vs_96.png
>
>
> Testing on larger clusters has not had the desired throughput increases.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
