You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2015/07/19 10:41:04 UTC
[jira] [Updated] (TAJO-1343) Improve the memory usage of physical
executors
[ https://issues.apache.org/jira/browse/TAJO-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jihoon Son updated TAJO-1343:
-----------------------------
Attachment: master-memory.png
1343-memory.png
Attached profiling results.
> 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 bugs.
> *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
(v6.3.4#6332)