Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4F94417766 for ; Wed, 1 Apr 2015 16:38:53 +0000 (UTC) Received: (qmail 27518 invoked by uid 500); 1 Apr 2015 16:38:53 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 27486 invoked by uid 500); 1 Apr 2015 16:38:53 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 27474 invoked by uid 99); 1 Apr 2015 16:38:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2015 16:38:53 +0000 Date: Wed, 1 Apr 2015 16:38:53 +0000 (UTC) From: "Vinay Shukla (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-6646) Spark 2.0: Rearchitecting Spark for Mobile Platforms 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/SPARK-6646?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1439= 0950#comment-14390950 ]=20 Vinay Shukla commented on SPARK-6646: ------------------------------------- This use case can benefit from running Spark inside a Mobile App Server. An= App server that takes care of horizontal issues such as security, networki= ng, etc will allow Spark to focus on the real hard problem of data processi= ng in a lightening fast manner. There is another idea of using having Spark leverage [parallel quantum comp= uting | http://people.csail.mit.edu/nhm/pqc.pdf] but I suppose that calls f= or another JIRA. > Spark 2.0: Rearchitecting Spark for Mobile Platforms > ---------------------------------------------------- > > Key: SPARK-6646 > URL: https://issues.apache.org/jira/browse/SPARK-6646 > Project: Spark > Issue Type: Improvement > Components: Project Infra > Reporter: Reynold Xin > Assignee: Reynold Xin > Priority: Blocker > Attachments: Spark on Mobile - Design Doc - v1.pdf > > > Mobile computing is quickly rising to dominance, and by the end of 2017, = it is estimated that 90% of CPU cycles will be devoted to mobile hardware. = Spark=E2=80=99s project goal can be accomplished only when Spark runs effic= iently for the growing population of mobile users. > Designed and optimized for modern data centers and Big Data applications,= Spark is unfortunately not a good fit for mobile computing today. In the p= ast few months, we have been prototyping the feasibility of a mobile-first = Spark architecture, and today we would like to share with you our findings.= This ticket outlines the technical design of Spark=E2=80=99s mobile suppor= t, and shares results from several early prototypes. > Mobile friendly version of the design doc: https://databricks.com/blog/20= 15/04/01/spark-2-rearchitecting-spark-for-mobile.html -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org