drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-1942) Improve off-heap memory usage tracking
Date Wed, 12 Aug 2015 16:25:46 GMT

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

ASF GitHub Bot commented on DRILL-1942:

GitHub user cwestin opened a pull request:


    DRILL-1942-templates: template changes with a few related dependencies.

    Changes to template files in the allocator branch, along with a few related dependencies.
    Unit tests pass, and regression suite passes.

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

    $ git pull https://github.com/cwestin/incubator-drill alloc-templates

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


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

    This closes #108
commit d7f949950143e4f32001d852e8e6b209db57d271
Author: Chris Westin <cwestin@yahoo.com>
Date:   2015-08-11T22:18:36Z

    DRILL-1942-templates: template changes with a few related dependencies.


> Improve off-heap memory usage tracking
> --------------------------------------
>                 Key: DRILL-1942
>                 URL: https://issues.apache.org/jira/browse/DRILL-1942
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Relational Operators
>            Reporter: Chris Westin
>            Assignee: Chris Westin
>             Fix For: 1.2.0
>         Attachments: DRILL-1942.1.patch.txt, DRILL-1942.2.patch.txt, DRILL-1942.3.patch.txt
> We're using a lot more memory than we think we should. We may be leaking it, or not releasing
it as soon as we could. 
> This is a call to come up with some improved tracking so that we can get statistics out
about exactly where we're using it, and whether or not we can release it earlier.

This message was sent by Atlassian JIRA

View raw message