| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Aaron J(dot) Seigo" <aaron(at)gtv(dot)ca> |
| Cc: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] Hardware optimising |
| Date: | 1999-08-27 00:12:23 |
| Message-ID: | 199908270012.UAA05593@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> as for the processor, this will see an increase, of course. note,
> however, that since PostgreSQL is _not_ multithreaded, that it will run
> only on one of the processors. (i'm about to assume you are using linux
> here... 'scuse me if i'm wrong) however, the good news is that you can
> encourage linux (through the scheduler) to run postgres on one of the
> processors and everything else on the other one. this should give the
> database its own processor more oft than not. things may still drift,
> etc... but it will be better this way....
Different backends can use different CPU's, no problem.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Lewis | 1999-08-27 00:32:44 | Re: [GENERAL] Hardware optimising |
| Previous Message | sam smith | 1999-08-26 23:45:06 | PL/pgSQL and arrays |