hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13291) Lift the scan ceiling
Date Mon, 06 Apr 2015 17:39:13 GMT

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

Andrew Purtell commented on HBASE-13291:
----------------------------------------

bq. interesting how different the picture perf top and flight recorder present... same basic
cast of characters but attribution is wildly different

Guessing: perf top isn't aware like flight recorder on how HotSpit can de- and re-optimize
methods. (It's a lovely hack though.) If you look in the perf map file in /tmp you might find
several addresses for the "same" JIT-ed Java method. perf doesn't know the invocation count
for the method should be aggregated from more than one emitted location, but I suspect FR
does. Let me make a note to research if this is true or not.

> Lift the scan ceiling
> ---------------------
>
>                 Key: HBASE-13291
>                 URL: https://issues.apache.org/jira/browse/HBASE-13291
>             Project: HBase
>          Issue Type: Improvement
>          Components: Scanners
>    Affects Versions: 1.0.0
>            Reporter: stack
>            Assignee: stack
>         Attachments: 13291.hacks.txt, 13291.inlining.txt, Screen Shot 2015-03-26 at 12.12.13
PM.png, Screen Shot 2015-03-26 at 3.39.33 PM.png, hack_to_bypass_bb.txt, nonBBposAndInineMvccVint.txt,
q (1).png, scan_no_mvcc_optimized.svg, traces.7.svg, traces.filterall.svg, traces.nofilter.svg,
traces.small2.svg, traces.smaller.svg
>
>
> Scanning medium sized rows with multiple concurrent scanners exhibits interesting 'ceiling'
properties. A server runs at about 6.7k ops a second using 450% of possible 1600% of CPUs
 when 4 clients each with 10 threads doing scan 1000 rows.  If I add '--filterAll' argument
(do not return results), then we run at 1450% of possible 1600% possible but we do 8k ops
a second.
> Let me attach flame graphs for two cases. Unfortunately, there is some frustrating dark
art going on. Let me try figure it... Filing issue in meantime to keep score in.



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

Mime
View raw message