You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Michael Miller (JIRA)" <ji...@apache.org> on 2017/05/04 20:21:04 UTC
[jira] [Resolved] (ACCUMULO-3079) improve system iterator
performance by collapsing call stack
[ https://issues.apache.org/jira/browse/ACCUMULO-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Miller resolved ACCUMULO-3079.
--------------------------------------
Resolution: Fixed
> improve system iterator performance by collapsing call stack
> ------------------------------------------------------------
>
> Key: ACCUMULO-3079
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3079
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Adam Fuchs
> Assignee: Michael Miller
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: iterator_performance_20140822_1.patch, iterator_performance_test_harness.tar.gz
>
> Time Spent: 12.5h
> Remaining Estimate: 0h
>
> System iterators are at the core of the tightest loops in Accumulo, handling every key/value pair that traverses through a scan or a compaction. In many cases, iterators are the current performance bottleneck for Accumulo. Every bit that we can improve performance in the iterators translates into better performance for Accumulo.
> There are several strategies that can be applied to the current code base to improve performance, including:
> # Inlining calls that are hard for the JVM to inline at runtime
> # Moving checks for null outside of tight loops when they are invariants within the loop
> # Eliminating "no-op" iterators at iterator tree construction time
> # Making frequently used and assigned-once objects final (like iterator sources)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)