From issues-return-8221-archive-asf-public=cust-asf.ponee.io@systemml.apache.org Fri Apr 20 14:17:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id F2FE418076D for ; Fri, 20 Apr 2018 14:17:05 +0200 (CEST) Received: (qmail 25086 invoked by uid 500); 20 Apr 2018 12:17:05 -0000 Mailing-List: contact issues-help@systemml.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@systemml.apache.org Delivered-To: mailing list issues@systemml.apache.org Received: (qmail 25077 invoked by uid 99); 20 Apr 2018 12:17:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2018 12:17:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 222D4C101F for ; Fri, 20 Apr 2018 12:17:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HVtSZr79gbWF for ; Fri, 20 Apr 2018 12:17:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 972F65F54E for ; Fri, 20 Apr 2018 12:17:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4B272E0F1F for ; Fri, 20 Apr 2018 12:17:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A7787241CE for ; Fri, 20 Apr 2018 12:17:00 +0000 (UTC) Date: Fri, 20 Apr 2018 12:17:00 +0000 (UTC) From: "LI Guobao (JIRA)" To: issues@systemml.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SYSTEMML-1313) Parfor broadcast exploitation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SYSTEMML-1313?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1= 6445646#comment-16445646 ]=20 LI Guobao commented on SYSTEMML-1313: ------------------------------------- Hi [~mboehm7], I have introduce the runtime support and I'd like to run a t= est for=C2=A0it. And which test can I take? Should I install a yarn cluster= so that the parfor can be executed in mode `remote_spark`? > Parfor broadcast exploitation > ----------------------------- > > Key: SYSTEMML-1313 > URL: https://issues.apache.org/jira/browse/SYSTEMML-1313 > Project: SystemML > Issue Type: Sub-task > Components: APIs, Runtime > Reporter: Matthias Boehm > Assignee: LI Guobao > Priority: Major > > The parfor optimizer may decide to execute the entire loop as a remote Sp= ark job to utilize cluster parallelism. In this case all inputs to the parf= or body (i.e., variable that are created or read outside of the parfor body= but used or overwritten inside) are read from HDFS. In the past there was = an issue of redundant reads, which has been addressed with SYSTEMML-1879. H= owever, the direct use of Spark broadcast variables would likely improve pe= rformance, especially in clusters with many nodes. > This task aims to leverage Spark broadcast variables for all parfor input= s. In detail this entails two major aspects. First, we need runtime support= to optionally broadcast the inputs via broadcast variables in {{RemoteParF= orSpark}} and obtain them from these broadcast variables in {{RemoteParForS= parkWorker}} without causing unnecessary eviction. In contrast, to the exis= ting broadcast primitives, we don't need to blockify the matrix because the= matrix is accessed in full by in-memory operations. Second, this requires = an extension of the parfor optimizer to reason about scenarios where it is = safe to use broadcast because these broadcasts cause additional memory requ= irements since they act as pinned in memory matrices. This second task has = likely overlap with SYSTEMML-1349 which requires a similar reasoning to han= dle shared reads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)