hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-576) Investigate IPC performance
Date Wed, 08 Oct 2008 22:31:44 GMT

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

stack commented on HBASE-576:

Did a little informal test.  I put up 4 regionservers in my little cluster, loaded it w/ million
rows then did random reading against the million rows from a remote client (different network).
  I tried with different numbers of clients.  While the clients ran, I watched them in the
profiler and I watched the requests/second up on the master node.  Here's a rough recording
of what I saw up on the master requests/second.

1 client - 230/s
4 clients - 630/s
16 clients - 1050/s
32 clients - 2460/s
64 clients - 2770/s
128 clients - 1150/s
256 clients - 1100/s

For the 128 and 256 clients, I could most threads blocked in the client.   According to the
profiler, when 4 or more clients, the RPC threads are spending all their time i/o on the net.
 That 4 clients don't max the request/second would seem to say servers can easily carry more
than one client request at a time (duh).  When the number of clients goes > 64, client
looks like it starts to trip itself up spending bulk of time blocked.

> Investigate IPC performance
> ---------------------------
>                 Key: HBASE-576
>                 URL: https://issues.apache.org/jira/browse/HBASE-576
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.1.0, 0.1.1, 0.1.2, 0.2.0
>            Reporter: Jim Kellerman
>            Assignee: stack
>         Attachments: htd.patch, pe.patch
> Turning off all file I/O, and running the PerformanceEvaluation test, of 1,048,576 sequential
writes to HBase managed to achieve only 7,285 IPCs per second.
> Running PerformanceEvaluation sequential write test modified to do an abort instead of
a commit, it was possible to do 68,337 operations per second. We are obviously spending a
lot of time doing IPCs. 
> We need to investigate to find the bottleneck. Marshalling and unmarshalling? Socket
setup and teardown?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message