You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/08/06 19:13:00 UTC
[jira] [Updated] (HBASE-27276) Reduce reflection overhead in Filter deserialization
[ https://issues.apache.org/jira/browse/HBASE-27276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Beaudreault updated HBASE-27276:
--------------------------------------
Summary: Reduce reflection overhead in Filter deserialization (was: Reduce reflection usage in Filter deserialization)
> Reduce reflection overhead in Filter deserialization
> ----------------------------------------------------
>
> Key: HBASE-27276
> URL: https://issues.apache.org/jira/browse/HBASE-27276
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Priority: Major
> Attachments: async-prof-pid-9037-cpu-1.html
>
>
> Running hbase 2.4.x, I recently profiled one of our clusters which does a very high volume of random reads. An astonishing 12% of CPU time was just spent deserializing in ProtobufUtil.toFilter.
> One immediate thought would be to cache String -> Class mappings. Currently Class.forName shows up multiple times (6 in my example) in the profile, each time taking over 1%. I think this is partially due to using FilterList in this example.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)