Accumulo
  1. Accumulo
  2. ACCUMULO-3088

StatsIterator readCounter could be more accurate

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      When testing seek performance I noticed that the read count displayed on Accumulo's monitor page registered zero entries read per second and a positive number of entries per second returned. This should not be possible. There is a fencepost error in the StatsIterator where seeks don't count as entries read.

      Successful completion of this ticket should handle the cases where a seek returns no entries, as well as where next is never called on an iterator.

      The cost of incrementing an AtomicLong is something like 10ns, which is at least an order of magnitude more than the desired overhead. The current way of batching updates to the read counter should be preserved for performance.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Adam Fuchs
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development