Skip site navigation (1) Skip section navigation (2)

[ Progress on scaling of FreeBSD on 8 CPU systems]

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: pgsql-performance(at)postgresql(dot)org
Subject: [ Progress on scaling of FreeBSD on 8 CPU systems]
Date: 2007-02-27 18:26:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Thought I'd pass this along, since the Linux vs FreeBSD performance
question comes up fairly regularly...

BTW, I've already asked about benchmarking with PostgreSQL, so please
don't go over there making trouble. :)

----- Forwarded message from Kris Kennaway <kris(at)obsecurity(dot)org> -----

X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on
X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_50,
	FORGED_RCVD_HELO,SPF_PASS autolearn=no version=3.1.6
Date: Sat, 24 Feb 2007 16:31:11 -0500
From: Kris Kennaway <kris(at)obsecurity(dot)org>
To: current(at)FreeBSD(dot)org, smp(at)FreeBSD(dot)org, hackers(at)FreeBSD(dot)org
User-Agent: Mutt/
Subject: Progress on scaling of FreeBSD on 8 CPU systems
Precedence: list
Errors-To: owner-freebsd-current(at)freebsd(dot)org

Now that the goals of the SMPng project are complete, for the past
year or more several of us have been working hard on profiling FreeBSD
in various multiprocessor workloads, and looking for performance
bottlenecks to be optimized.

We have recently made significant progress on optimizing for MySQL
running on an 8-core amd64 system. The graph of results may be found

This shows the graph of MySQL transactions/second performed by a
multi-threaded client workload against a local MySQL database with
varying numbers of client threads, with identically configured FreeBSD
and Linux systems on the same machine.

The test was run on FreeBSD 7.0, with the latest version of the ULE
2.0 scheduler, the libthr threading library, and an uncommitted patch
from Jeff Roberson [1] that addresses poor scalability of file
descriptor locking (using a new sleepable mutex primitive); this patch
is responsible for almost all of the performance and scaling
improvements measured.  It also includes some other patches (collected
in my kris-contention p4 branch) that have been shown to help
contention in MySQL workloads in the past (including a UNIX domain
socket locking pushdown patch from Robert Watson), but these were
shown to only give small individual contributions, with a cumulative
effect on the order of 5-10%.

With this configuration we are able to achieve performance that is
consistent with Linux at peak (the graph shows Linux 2% faster, but
this is commensurate with the margin of error coming from variance
between runs, so more data is needed to distinguish them), with 8
client threads (=1 thread/CPU core), and significantly outperforms
Linux at higher than peak loads, when running on the same hardware.

Specifically, beyond 8 client threads FreeBSD has only minor
performance degradation (an 8% drop from peak throughput at 8 clients
to 20 clients), but Linux collapses immediately above 8 threads, and
above 14 threads asymptotes to essentially single-threaded levels.  At
20 clients FreeBSD outperforms Linux by a factor of 4.

We see this result as part of the payoff we are seeing from the hard
work of many developers over the past 7 years.  In particular it is a
significant validation of the SMP and locking strategies chosen for
the FreeBSD kernel in the post-FreeBSD 4.x world.

More configuration details and discussion about the benchmark may be
found here:


----- End forwarded message -----

Jim C. Nasby, Database Architect                decibel(at)decibel(dot)org 
Give your computer some brain candy! Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-performance by date

Next:From: Joe UhlDate: 2007-02-27 18:28:13
Subject: Re: Opinions on Raid
Previous:From: Andrew - SupernewsDate: 2007-02-27 17:56:25
Subject: Re: Postgres performance Linux vs FreeBSD

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group