From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751540AbZIMWDU (ORCPT ); Sun, 13 Sep 2009 18:03:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751173AbZIMWDT (ORCPT ); Sun, 13 Sep 2009 18:03:19 -0400 Received: from swampdragon.chaosbits.net ([90.184.90.115]:15148 "EHLO swampdragon.chaosbits.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751033AbZIMWDS (ORCPT ); Sun, 13 Sep 2009 18:03:18 -0400 Date: Mon, 14 Sep 2009 00:03:20 +0200 (CEST) From: Jesper Juhl To: Mike Galbraith cc: Ingo Molnar , Tony Luck , Linus Torvalds , linux-kernel@vger.kernel.org, Peter Zijlstra Subject: Re: [GIT PULL] sched/core for v2.6.32 In-Reply-To: <1252824114.16650.130.camel@marge.simson.net> Message-ID: References: <20090911192505.GA20006@elte.hu> <12c511ca0909111924s42d000dsbf378009d9434ddc@mail.gmail.com> <20090912054917.GB9420@elte.hu> <1252824114.16650.130.camel@marge.simson.net> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 13 Sep 2009, Mike Galbraith wrote: > On Sun, 2009-09-13 at 00:07 +0200, Jesper Juhl wrote: > > On Sat, 12 Sep 2009, Ingo Molnar wrote: > > > > > > It was a statistical property based on performance considerations - > > > and now we flipped it around based on latency and for kbuild > > > performance/throughput reasons: Serge Belyshev reported a 7% > > > increase on a quad due to this change and i measured a 1.5% > > > peak-kbuild performance increase. > > > > > Impressive. I wouldn't have expected that much gain by running the parent > > first. Actually I personally would have expected child-first to perform > > better since (in my experience) it's usually the child that's just forked > > that matters the most. > > How can waiting for child1 to run a bit before forking off child2 _not_ > hurt? The parent is the worker bee creator, the queen bee if you will. > Seems to me that making the queen wait until one egg hatches and ages a > bit before laying another egg is a very bad plan if the goal is to have > a hive full of short lived worker bees. > When I wrote the above, I was thinking of one specific case; a server that receives a request, forks off a child to handle the request and the performance we measure is of how long it takes to handle that single request - and in that specific scenario we want the child to run as soon as possible. -- Jesper Juhl http://www.chaosbits.net/ Plain text mails only, please http://www.expita.com/nomime.html Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html