From: | Andy Lewis <alewis(at)roundnoon(dot)com> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "Aaron J(dot) Seigo" <aaron(at)gtv(dot)ca>, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] Hardware optimising |
Date: | 1999-08-27 00:32:44 |
Message-ID: | Pine.LNX.4.05.9908261932230.10350-100000@rns.roundnoon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What scheduler are we speaking of here?
Andy
On Thu, 26 Aug 1999, Bruce Momjian wrote:
> > 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 | Anand Surelia | 1999-08-27 00:43:06 | Pg.pm for Windows? |
Previous Message | Bruce Momjian | 1999-08-27 00:12:23 | Re: [GENERAL] Hardware optimising |