LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "debian developer" <debiandev@gmail.com>
To: "Stephen Cuppett" <cuppett@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Performance versus FreeBSD 7.0
Date: Thu, 6 Mar 2008 22:59:44 +0530	[thread overview]
Message-ID: <f24d23310803060929k30f17947mda54a6de2bc294a3@mail.gmail.com> (raw)
In-Reply-To: <316a20a40802290538g55c4171y7cdbcb3a9c1d0f1b@mail.gmail.com>

On Fri, Feb 29, 2008 at 7:08 PM, Stephen Cuppett <cuppett@gmail.com> wrote:
> Not lobbing the first artillery shell by any means, but I saw this
>  bullet on the FreeBSD release announcement:
>
>  # Dramatic improvements in performance and SMP scalability shown by
>  various database and other benchmarks, in some cases showing peak
>  performance improvements as high as 350% over FreeBSD 6.X under normal
>  loads and 1500% at high loads. When compared with the best performing
>  Linux kernel (2.6.22 or 2.6.24) performance is 15% better. Results are
>  from benchmarks used to analyze and improve system performance,
>  results with your specific work load may vary. Some of the changes
>  that contribute to this improvement are:
>
>     * The 1:1 libthr threading model is now the default.
>     * Finer-grained IPC, networking, and scheduler locking.
>     * A major focus on optimizing the SMP architecture that was put in
>  place during the 5.x and 6.x branches.
>
>  Some benchmarks show linear scaling up to 8 CPUs. Many workloads see a
>  significant performance improvement with multicore systems.
>
>  The whole thing is available at:
>
>  http://www.freebsd.org/releases/7.0R/announce.html
>
>  However, their site is pretty scant on details about those benchmarks.
>   Was just curious if anybody on this list had any input or links on
>  the metrics, the hardware, the workloads, how was Linux or FreeBSD
>  tuned, knew more information, could point me to the stats....

The benchmarks are posted here

http://people.freebsd.org/~kris/scaling/7.0%20Preview.pdf

page no 17-20.

A funny quote on CFS from above (page 19)

"The new CFS scheduler in 2.6.23 is "Completely Fair"...to
FreeBSD" :)

good to see some competition at last :D

  parent reply	other threads:[~2008-03-06 17:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 13:38 Stephen Cuppett
2008-02-29 14:54 ` Diego Calleja
2008-03-03 13:04   ` Nick Piggin
2008-03-03 19:02     ` Cyrus Massoumi
2008-03-03 19:24       ` Nick Piggin
2008-03-03 22:47         ` Cyrus Massoumi
2008-03-03 23:23       ` Andi Kleen
2008-03-04  5:51         ` Cyrus Massoumi
2008-03-06 12:53         ` Nick Piggin
2008-03-06 13:12           ` Andi Kleen
2008-03-03 12:34 ` Andi Kleen
2008-03-06 17:29 ` debian developer [this message]
2008-03-06 17:34   ` debian developer
     [not found] <a2dDb-60y-29@gated-at.bofh.it>
     [not found] ` <a2eSt-7UK-1@gated-at.bofh.it>
2009-01-25 10:07   ` Lx

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f24d23310803060929k30f17947mda54a6de2bc294a3@mail.gmail.com \
    --to=debiandev@gmail.com \
    --cc=cuppett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Performance versus FreeBSD 7.0' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).