[jira] [Commented] (DRILL-1942) Improve off-heap memory usage tracking

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user cwestin opened a pull request:

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

    DRILL-1942-concurrency-test: new smoke test for concurrent query exec…

    …ution;
    
    useful to checking on the new allocator's locking schemes.
    
    Made the SilentListener in BaseTestQuery.java public so it could be reused. Added new TestTpchDistributedConcurrent.java as a unit test. No other changes.
    
    Unit tests (mvn install) pass.

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

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

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

    https://github.com/apache/drill/pull/105.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 #105
    
----
commit 22e7f4e46310cea1b0b6df6beaded67795325892
Author: Chris Westin <cw...@yahoo.com>
Date:   2015-08-07T00:09:26Z

    DRILL-1942-concurrency-test: new smoke test for concurrent query execution;
    useful to checking on the new allocator's locking schemes.

----


> 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
(v6.3.4#6332)