hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6338) Cache Method in RPC handler
Date Wed, 16 Nov 2016 21:59:58 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-6338.
--------------------------
    Resolution: Not A Problem

We don't need this anymore [~aoxiang], right, in protobuf context and Service with all the
static calls? Resolving as not-a-problem. Reopen if still needed or open new issue to do same
in new context.

> Cache Method in RPC handler
> ---------------------------
>
>                 Key: HBASE-6338
>                 URL: https://issues.apache.org/jira/browse/HBASE-6338
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.94.3
>            Reporter: binlijin
>         Attachments: HBASE-6338-90-2.patch, HBASE-6338-90.patch, HBASE-6338-92-2.patch,
HBASE-6338-92.patch, HBASE-6338-94-2.patch, HBASE-6338-94.patch, HBASE-6338-trunk-2.patch,
HBASE-6338-trunk.patch
>
>
> Every call in rpc handler a Method will be created, if we cache the method will improve
a little.
> I test with 0.90, Average Class.getMethod(String name, Class... parameterTypes) cost
4780 ns , if we cache it cost 2620 ns.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message