Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2079F109B4 for ; Mon, 27 Jan 2014 06:15:04 +0000 (UTC) Received: (qmail 93802 invoked by uid 500); 27 Jan 2014 06:15:03 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 93767 invoked by uid 500); 27 Jan 2014 06:15:03 -0000 Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list dev@aurora.incubator.apache.org Received: (qmail 93758 invoked by uid 99); 27 Jan 2014 06:15:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jan 2014 06:15:03 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 27 Jan 2014 06:15:00 +0000 Received: (qmail 93690 invoked by uid 99); 27 Jan 2014 06:14:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jan 2014 06:14:39 +0000 Date: Mon, 27 Jan 2014 06:14:39 +0000 (UTC) From: "Joe Smith (JIRA)" To: dev@aurora.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AURORA-117) Scheduler performance issues with very large jobs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AURORA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Smith updated AURORA-117: ----------------------------- Labels: O1 (was: O2) > Scheduler performance issues with very large jobs > ------------------------------------------------- > > Key: AURORA-117 > URL: https://issues.apache.org/jira/browse/AURORA-117 > Project: Aurora > Issue Type: Task > Components: Reliability, Scheduler > Reporter: Bill Farner > Labels: O1 > > The scheduler tends to have performance issues when scheduling very large jobs. We've observed this with jobs exceeding 2000 instances. The {{TaskScheduler}} thread tends to consume a large amount of CPU (100%, limited by the global storage lock). Current hypothesis is that the majority of the time is spent satisfying diversity constraints (rack, machine), which require expensive queries. -- This message was sent by Atlassian JIRA (v6.1.5#6160)