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

ASF GitHub Bot commented on DRILL-5270:
---------------------------------------

GitHub user kkhatua opened a pull request:

    https://github.com/apache/drill/pull/755

    DRILL-5270: Improve loading of profiles listing in the WebUI

    Using Hadoop API to filter and reduce profile list load time
    Using an in-memory treeSet-based cache, maintain the list of most recent
    profiles.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kkhatua/drill DRILL-5270

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/755.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #755
    
----
commit a5f20643850ad399622e5df9a6f37713545dc7a6
Author: Kunal Khatua <[email protected]>
Date:   2017-02-22T01:20:48Z

    DRILL-5270: Improve loading of profiles listing in the WebUI
    
    Using Hadoop API to filter and reduce profile list load time
    Using an in-memory treeSet-based cache, maintain the list of most recent
    profiles.

----


> Improve loading of profiles listing in the WebUI
> ------------------------------------------------
>
>                 Key: DRILL-5270
>                 URL: https://issues.apache.org/jira/browse/DRILL-5270
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Web Server
>    Affects Versions: 1.9.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>             Fix For: 1.10.0
>
>
> Currently, as the number of profiles increase, we reload the same list of 
> profiles from the FS.
> An ideal improvement would be to detect if there are any new profiles and 
> only reload from the disk then. Otherwise, a cached list is sufficient.
> For a directory of 280K profiles, the load time is close to 6 seconds on a 32 
> core server. With the caching, we can get it down to as much as a few 
> milliseconds.
> To render the cache as invalid, we inspect the last modified time of the 
> directory to confirm whether a reload is needed. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to