tajo-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] (TAJO-1343) Improve the memory usage of physical executors
Date Mon, 20 Jul 2015 03:38:04 GMT

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

ASF GitHub Bot commented on TAJO-1343:

Github user jihoonson commented on the pull request:

    @jinossy thanks for your review. 
    I've added ```clear()``` in ```put()``` method because I was considering unexpected errors
when the datum array of different length is put.
    As you think, this may accompany large overhead. I will remove it after some test.

> Improve the memory usage of physical executors
> ----------------------------------------------
>                 Key: TAJO-1343
>                 URL: https://issues.apache.org/jira/browse/TAJO-1343
>             Project: Tajo
>          Issue Type: Improvement
>          Components: physical operator
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>            Priority: Critical
>             Fix For: 0.11.0
>         Attachments: 1343-memory.png, master-memory.png
> *Introduction*
> Basically, the tuple instance is maintained as a singleton in physical operators. However,
there are some memory-based operator types which need to keep multiple tuples in the memory.
In these operators, multiple instances must be created for each tuple.
> *Problem*
> Currently, there are some temporal routines to avoid unexpected problems due to the singleton
instance of tuple. However, the methodology is inconsistent and complex, which causes unexpected
> *Solution*
> A consistent methodology is needed to handle this problem. Only the operators that keep
multiple tuples in memory must maintain those tuples with separate instances.

This message was sent by Atlassian JIRA

View raw message