Re: Machine available for community use

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Gavin M(dot) Roy" <gavinmroy(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Machine available for community use
Date: 2007-11-02 21:11:30
Message-ID: 26917.1194037890@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah, I'd vote for people just building private PG installations in
>> their own home directories. I am not aware of any performance-testing
>> reason why we'd want a shared installation, and given that people are
>> likely to be testing many different code variants, a shared

> The only caveat here is that our thinking was that the actual arrays
> would be able to be re-provisioned all the time. E.g; test with RAID 10
> with x stripe size, Software RAID 6, what is the real difference
> between 28 spindles with RAID 5 versus 10?

Well, we need some workspace that won't go away when that happens.
I'd suggest that the OS and people's home directories be mounted on
a "permanent" partition with plenty of space for source code, say a
few tens of GB, and then there be a farm of data workspace that's
understood to be transient and can be reconfigured as needed for tests
like that.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2007-11-02 21:13:20 Re: Machine available for community use
Previous Message Alvaro Herrera 2007-11-02 21:00:58 Re: AutoVacuum Behaviour Question