From commits-return-13732-archive-asf-public=cust-asf.ponee.io@airflow.incubator.apache.org Mon Apr 9 13:29:03 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 14F0C180645 for ; Mon, 9 Apr 2018 13:29:02 +0200 (CEST) Received: (qmail 41089 invoked by uid 500); 9 Apr 2018 11:29:02 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 41080 invoked by uid 99); 9 Apr 2018 11:29:02 -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; Mon, 09 Apr 2018 11:29:02 +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 90BC1C1B1B for ; Mon, 9 Apr 2018 11:29:01 +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-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id VdPmt33lY4At for ; Mon, 9 Apr 2018 11:29:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CBEEB5F18F for ; Mon, 9 Apr 2018 11:29:00 +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 51B8FE0153 for ; Mon, 9 Apr 2018 11:29:00 +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 0E912241C4 for ; Mon, 9 Apr 2018 11:29:00 +0000 (UTC) Date: Mon, 9 Apr 2018 11:29:00 +0000 (UTC) From: =?utf-8?Q?M=C3=A1t=C3=A9_Szab=C3=B3_=28JIRA=29?= To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-2128) 'Tall' DAGs scale worse than 'wide' DAGs 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/AIRFLOW-2128?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 430399#comment-16430399 ]=20 M=C3=A1t=C3=A9 Szab=C3=B3 commented on AIRFLOW-2128: ------------------------------------- {code:java} min_file_process_interval =3D 0 {code} I believe this is the default setting. > 'Tall' DAGs scale worse than 'wide' DAGs > ---------------------------------------- > > Key: AIRFLOW-2128 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2128 > Project: Apache Airflow > Issue Type: Bug > Components: DAG, DagRun, scheduler > Affects Versions: 1.9.0 > Reporter: M=C3=A1t=C3=A9 Szab=C3=B3 > Priority: Major > Labels: performance, usability > Attachments: tall_dag.py, wide_dag.py > > > Tall DAG =3D a DAG with long chains of dependencies, e.g.: 0 -> 1 -> 2 ->= ... -> 998 -> 999 > Wide DAG =3D a DAG with many short, parallel dependencies e.g. 0 -> 1; 0= -> 2; ... 0 -> 999 > Take a super simple=C2=A0case where both graphs are of 1000 tasks, and al= l the tasks are just "sleep 0.03" bash commands (see the attached files). > With the default SequentialExecutor (without paralellism), I would expec= t my 2 example DAGs to take (approximately) the same time to run, but appar= ently this is not the case. > For the wide DAG it was about 80 successfully executed tasks in 10 minute= s, for the tall one it was 0. > This anomaly also seem to affect the web UI. Opening up the graph view or= the tree view for the wide DAG takes about 6 seconds on my machine, but fo= r the tall one it takes significantly longer, in fact currently it does not= load at all. -- This message was sent by Atlassian JIRA (v7.6.3#76005)