[
https://issues.apache.org/jira/browse/HBASE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637380#action_12637380
]
stack commented on HBASE-576:
-----------------------------
Thanks for the patch J-D. Went in w/ some slop. I removed an unneeded import.
Any chance of your making a patch to replace all instances of ObjectWritable in
HbaseRPC with HbaseObjectWritable? Its a silly regression on my part broken in
the below commit:
{code}
r679212 | stack | 2008-07-23 15:13:23 -0700 (Wed, 23 Jul 2008) | 1 line
HBASE-770 Update HBaseRPC to match hadoop 0.17 RPC
{code}
I did some more timings. An instance with 3 threads did 936/second random reads
which is about twice a single thread and about 2/3rds 8 threads.
> 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.
