You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/04/24 01:30:00 UTC
[jira] [Resolved] (KUDU-1977) MetaCache cache hits should avoid ref
count incr/decr
[ https://issues.apache.org/jira/browse/KUDU-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved KUDU-1977.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
Fixed in b2b8fb74dc564b5e55af6406982e80f2efa19f3c
> MetaCache cache hits should avoid ref count incr/decr
> -----------------------------------------------------
>
> Key: KUDU-1977
> URL: https://issues.apache.org/jira/browse/KUDU-1977
> Project: Kudu
> Issue Type: Improvement
> Components: client, perf
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Major
> Fix For: 1.8.0
>
>
> Looking at CPU consumption of a client using perf tools (including the new perf-c2c tool) I see that metacache hits in multi-threaded writers are rather slow because of the reference count increments and decrements on the MetaCache object.
> In the case of the cache hit, there's no real need to allocate the LookupRpc object, increment ref counts, and then decrement them. Instead we could move the fast-path check out of LookupRpc and save some CPU.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)