| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pg(at)fastcrypt(dot)com, Paul Tuckfield <paul(at)tuckfield(dot)com>, Anjan Dave <adave(at)vantage(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, Dirk Lutzebäck <lutzeb(at)aeccom(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Wierd context-switching issue on Xeon patch for 7.4.1 |
| Date: | 2004-04-22 18:11:43 |
| Message-ID: | 200404221111.43151.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tom,
> Having to recompile to run on single- vs dual-processor machines doesn't
> seem like it would fly.
Oh, I don't know. Many applications require compiling for a target
architecture; SQL Server, for example, won't use a 2nd processor without
re-installation. I'm not sure about Oracle.
It certainly wasn't too long ago that Linux gurus were esposing re-compiling
the kernel for the machine.
And it's not like they would *have* to re-compile to use PostgreSQL after
adding an additional processor. Just if they wanted to maximize peformance
benefit.
Also, this is a fairly rare circumstance, I think; to judge by my clients,
once a database server is in production nobody touches the hardware.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Bertheau | 2004-04-22 18:20:47 | Re: [pgsql-advocacy] MySQL vs PG TPC-H benchmarks |
| Previous Message | Tom Lane | 2004-04-22 17:55:53 | Re: Wierd context-switching issue on Xeon patch for 7.4.1 |