From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
---|---|
To: | "Nathan Wilhelmi" <wilhelmi(at)ucar(dot)edu>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Importance of CPU floating point performance... |
Date: | 2007-11-09 21:47:43 |
Message-ID: | D425483C2C5C9F49B5B7A41F8944154701000A8B@postal.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Nathan Wilhelmi
> Sent: Friday, November 09, 2007 12:01 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] Importance of CPU floating point performance...
>
> Hello - Trying to find out how much floating point operation
performance
> effects Postgres in general. Looking at some lower power machines that
> have good integer performance but not great floating point
performance,
> shared FPU across cpus. If we store, but don't use in query criteria,
> floating point numbers would Postgres perform the same as machine with
> dedicated FPUs per cpu? Anyone have any suggestions or horror stories
to
> share on this topic?
Like every database, CPU core count and cycle rate, disk speed and
memory size dominate the equation.
A fast 64 bit smp linux box with a ton of memory and the fastest
possible disk will give you top performance.
Here are some PG benchmarks:
http://tweakers.net/reviews/657/6
http://tweakers.net/reviews/657/5
http://www.spec.org/jAppServer2004/results/res2007q3/jAppServer2004-2007
0606-00065.html
Floating point performance will be nothing more than an afterthought for
most database performance situations.
From | Date | Subject | |
---|---|---|---|
Next Message | Todd A. Cook | 2007-11-09 22:06:33 | Is "query" a reserved word in 8.3 plpgsql? |
Previous Message | Bruce Momjian | 2007-11-09 21:20:17 | Re: [GENERAL] Crosstab Problems |