From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: [kris@obsecurity.org: Progress on scaling of FreeBSD on 8 CPU systems]
Date: Fri, 02 Mar 2007 10:35:01 -0600
Message-ID: <1172853301.20651.196.camel@state.g2switchworks.com> (raw)
In-Reply-To: <20070302150129.GF4885@alvh.no-ip.org>
References: <20070227182621.GE29041@decibel.org>
<20070302150129.GF4885@alvh.no-ip.org>
On Fri, 2007-03-02 at 09:01, Alvaro Herrera wrote:
> > From: Kris Kennaway <kris@obsecurity.org>
>
> > We have recently made significant progress on optimizing for MySQL
> > running on an 8-core amd64 system. The graph of results may be found
> > here:
> >
> > http://www.freebsd.org/~kris/scaling/scaling.png
> >
> > 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.
>
> Interesting -- the MySQL/Linux graph is very similar to the graphs from
> the .nl magazine posted last year. I think this suggests that the
> "MySQL deficiency" was rather a performance bug in Linux, not in MySQL
> itself ...
I rather think it's a combination of how MySQL does things and Linux not
being optimized to handle that situation.
It may well be that the fixes to BSD have simply moved the point at
which performance dives off quickly from 50 connections to 300 or
something.
I'd really like to see freebsd tested on the 32 thread Sun CPU that had
such horrible performance with linux, and with many more threads to see
if there's still a cliff there somewhere, and to see where postgresql's
cliff would be as well. After all, the most interesting part of
performance graphs are the ones you see when the system is heading into
overload.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: smarlowe@g2switchworks.com, alvherre@commandprompt.com, decibel@decibel.org
Subject: Re: [kris@obsecurity.org: Progress on scaling of FreeBSD on 8 CPU systems]
In-Reply-To: <1172853301.20651.196.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox