[
https://issues.apache.org/jira/browse/ACCUMULO-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3088.
-----------------------------------------
Resolution: Abandoned
Closing old inactive issue; if this is still a problem, please create a new
issue or pull request at https://github.com/apache/accumulo
> StatsIterator readCounter could be more accurate
> ------------------------------------------------
>
> Key: ACCUMULO-3088
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3088
> Project: Accumulo
> Issue Type: Bug
> Reporter: Adam Fuchs
> Priority: Trivial
> Labels: newbie
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
