systemml-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "LI Guobao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYSTEMML-2482) Unexpected cleanup of list object
Date Thu, 02 Aug 2018 20:51:00 GMT

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

LI Guobao commented on SYSTEMML-2482:
-------------------------------------

[~mboehm7] well, sorry about the unspecific description. Actually, I just found that the data
status in list object is no longer used (i.e., null or array of false). Because, before that
commit, all the matrices of the list output will be pinned in the vars table and the pinned
status will be saved in this boolean array. And I just fix the problem of eviction by changing
the logic of cleanning up the list object with its data status.

> Unexpected cleanup of list object
> ---------------------------------
>
>                 Key: SYSTEMML-2482
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-2482
>             Project: SystemML
>          Issue Type: Bug
>            Reporter: LI Guobao
>            Priority: Major
>
> Some unexpected overhead occurred when running the {{*testParamservASPEpochDisjointContiguous*}}
in test {{*org.apache.sysml.test.integration.functions.paramserv.ParamservSparkNNTest*}}.
It took more time to finish the test in the case that the output of instruction is a list
which will be cleaned up after the execution. However, the matrices referenced by the list
should be pinned to avoid being cleaned up. And this issue is related to [SYSTEMML-2481|https://issues.apache.org/jira/browse/SYSTEMML-2481]




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message