accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-2837) Scanning empty table can be optimized
Date Thu, 28 May 2015 22:01:19 GMT


Christopher Tubbs updated ACCUMULO-2837:
         Priority: Major  (was: Critical)
    Fix Version/s:     (was: 1.7.1)
                       (was: 1.6.3)
       Issue Type: Improvement  (was: Bug)

Dropping priority and changing from "Bug" to "Improvement", because it doesn't appear to represent
an essential change.

[~kturner], is there more to be done on this? All the sub-tasks appear to be complete. Was
closing the parent simply overlooked, or did you want to add a sub-task to address the gzipping?

> Scanning empty table can be optimized
> -------------------------------------
>                 Key: ACCUMULO-2837
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.6.0
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>              Labels: performance
>             Fix For: 1.8.0
> I wrote an application that repeatedly scanned random rows in an empty table at one point.
 It did not know the table was empty.  I was jstacking the tserver and repeatedly saw stack
traces in a few places in the code. 
>  * the audit canScan method
>  * DefaultConfiguration.get
>  * Kept seeing Password token ungziping the password??????
> After fixing all of these issues (except for system token) I ran a simple test I saw
times go from ~1.7s to ~1.3s for a simple test I wrote to recreate this issue.
> I am not sure how much of an impact the gziping the password has.  I was just sampling
the stack traces manually.  I seems like I saw the password token gzip stack traces less frequently,
but I did catch it multiple jstack calls.

This message was sent by Atlassian JIRA

View raw message