systemml-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dylan Hutchison (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SYSTEMML-1834) Fusion plan enumeration: short-circuit costing by upper bound
Date Fri, 11 Aug 2017 08:54:00 GMT

     [ https://issues.apache.org/jira/browse/SYSTEMML-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dylan Hutchison resolved SYSTEMML-1834.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: SystemML 1.0

Merged in [#611|https://github.com/apache/systemml/pull/611]

> Fusion plan enumeration: short-circuit costing by upper bound
> -------------------------------------------------------------
>
>                 Key: SYSTEMML-1834
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-1834
>             Project: SystemML
>          Issue Type: Improvement
>          Components: Compiler
>            Reporter: Dylan Hutchison
>            Assignee: Dylan Hutchison
>            Priority: Minor
>             Fix For: SystemML 1.0
>
>
> An intensive step during codegen is enumerating alternative ways to fuse Hops together.
 The search process during this step computes the cost of many alternative plans. We should
speed up the search process by stopping the costing process early when a cost exceeds that
of the best plan found so far (an upper bound on the best plan in the search space).
> Measurements show that >60% of costed plans can be stopped early, at least for the
StratStats script. It is not clear how early the plans can be stopped, but there is a definite
benefit in search time (in seconds).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message