hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2219) stop using code mapping for method names in the RPC
Date Mon, 15 Feb 2010 09:23:27 GMT

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

ryan rawson commented on HBASE-2219:
------------------------------------

ok, doing multiple runs shows quite a bit less variance, and in some cases with this patch
is faster (?).

2219:
10/02/15 01:12:34 INFO hbase.PerformanceEvaluation: Finished randomRead in 23423ms at offset
0 for 100000 rows

10/02/15 01:13:20 INFO hbase.PerformanceEvaluation: Finished randomRead in 22861ms at offset
0 for 100000 rows

10/02/15 01:14:58 INFO hbase.PerformanceEvaluation: Finished randomRead in 22838ms at offset
0 for 100000 rows

10/02/15 01:15:39 INFO hbase.PerformanceEvaluation: Finished randomRead in 22851ms at offset
0 for 100000 rows

without:
10/02/15 01:19:27 INFO hbase.PerformanceEvaluation: Finished randomRead in 25250ms at offset
0 for 100000 rows

10/02/15 01:20:03 INFO hbase.PerformanceEvaluation: Finished randomRead in 23326ms at offset
0 for 100000 rows

10/02/15 01:20:35 INFO hbase.PerformanceEvaluation: Finished randomRead in 23010ms at offset
0 for 100000 rows

10/02/15 01:21:08 INFO hbase.PerformanceEvaluation: Finished randomRead in 23007ms at offset
0 for 100000 rows





> stop using code mapping for method names in the RPC
> ---------------------------------------------------
>
>                 Key: HBASE-2219
>                 URL: https://issues.apache.org/jira/browse/HBASE-2219
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.20.3
>            Reporter: ryan rawson
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2219-2.patch, HBASE-2219.patch
>
>
> since we use a sorted mapping of method names -> codes and send that over the wire,
even trivial changes, such as adding a new call, become wire-incompatible.  This means many
features which could easily have gone into a minor update must wait for a major update.  Eg:
2066, 1845, etc.
> This will increase on-wire overhead, but the compatibility is worth it I think.

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


Mime
View raw message