From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 18:46:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8694E7FF for ; Sat, 3 Nov 2012 18:46:20 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4F7A58FC0A for ; Sat, 3 Nov 2012 18:46:19 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so3284253pbb.13 for ; Sat, 03 Nov 2012 11:46:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version:content-type:x-gm-message-state; bh=aCkZBiJE+T2hHUJqUKjKauLEYLIvk3wUORaa8NyeMJk=; b=gfdciHoOz+C39gPA65Jb6G3/Xadhu3rXqFRA6q2ha5MdwKcM/uB4ikAy9aLEfo8yY6 sPar7vDVAqT97eYNSWDME2r53KqW3p5fM78nxtRbZni7nA2H0CJpWNzURxjjvKnJIv/z ha43yu7kiXnSkfQMcAh00eVK17JIRzaUsnH9GTnzqWzt61IuKOV2uyRab4elATefR0xU kventGH1/8mqi2ILWxzA7SK3L06mRdps2nvF3hJgh3E2beylL6JdWJTRViv+wVfNjIzG f/uGModeyh7XAGxJvPff6MN7zUFRn1RL75fOEmRiBCz582TlnouEXx8G6LlBVMyN6EVY nTBA== Received: by 10.66.78.97 with SMTP id a1mr15847887pax.32.1351968379397; Sat, 03 Nov 2012 11:46:19 -0700 (PDT) Received: from rrcs-66-91-135-210.west.biz.rr.com (rrcs-66-91-135-210.west.biz.rr.com. [66.91.135.210]) by mx.google.com with ESMTPS id ak10sm6859246pbd.24.2012.11.03.11.46.18 (version=SSLv3 cipher=OTHER); Sat, 03 Nov 2012 11:46:18 -0700 (PDT) Date: Sat, 3 Nov 2012 08:44:55 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: "O. Hartmann" Subject: Re: DragonFly vs FreeBSD scheduler In-Reply-To: <50953A1B.5050401@zedat.fu-berlin.de> Message-ID: References: <20121103091752.0000797f@unknown> <50953A1B.5050401@zedat.fu-berlin.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Gm-Message-State: ALoCoQl47b4Dqx7ou8WHFx5tr26DOPtxH/a8yWoVlUskVm4vh5Z6frFwcRIgJRo38gt30ORPwfsj Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2012 18:46:20 -0000 On Sat, 3 Nov 2012, O. Hartmann wrote: > Am 11/03/12 15:17, schrieb Mark Felder: >> On Sat, 3 Nov 2012 21:18:55 +0800 >> Alie Tan wrote: >> >>> Hi, >>> >>> No offence, just curious about scheduler and its functionality. >>> >>> What is the different between this two that makes FreeBSD performance far >>> behind DragonFly BSD? http://www.dragonflybsd.org/release32/ >>> >> >> I don't have any details but I do know that Dragonfly has been putting a lot of work into their scheduler. Hopefully some of that will trickle back our way. > > > Obviously they made the right decissions, but a single benchmark with a > DB server like postgresql doesn't tell the whole story. Let's see what > Phoronix will come up with. I'd like to see some more benchmarks of > DragonFly 3.2. > > I doubt that the DragonFly scheduler approaches will go/flow easily into > FreeBSD. But I'd like to see it, even dumping ULE for a better approach. It's not the scheduler. It's lock contention in the vm and buffer cache. The scheduler can only schedule what is runnable. We are working to address this problem. Thanks, Jeff > > > > > > > >