Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 1 Nov 2012 18:57:12 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1340315208.57312.1351796232497.JavaMail.jiratomcat@arcas>
In-Reply-To: <313327856.156088.1349209628641.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6925) Change socket write size from 8K to
 64K for HBaseServer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-6925:
--------------------------------------

I'd definitely be interested in the various changes that went into this.

HBASE-4956 just fixes Result.readFields to read the resultbuffer in 8k chunks?
Would that defeat the purpose of this change?

I can do some quick test on a single host, but that won't be very representative.
                
> Change socket write size from 8K to 64K for HBaseServer
> -------------------------------------------------------
>
>                 Key: HBASE-6925
>                 URL: https://issues.apache.org/jira/browse/HBASE-6925
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: Karthik Ranganathan
>            Assignee: Karthik Ranganathan
>            Priority: Critical
>             Fix For: 0.94.3, 0.96.0
>
>         Attachments: HBASE-6925.patch
>
>
> Creating a JIRA for this, but the change is trivial: change NIO_BUFFER_LIMIT from 8K to 64K in HBaseServer. This seems to increase scan throughput.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira