Re: Optimise PostgreSQL for fast testing

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: David Salisbury <salisbury(at)globe(dot)gov>, pgsql-general(at)postgresql(dot)org
Subject: Re: Optimise PostgreSQL for fast testing
Date: 2012-02-23 23:41:52
Message-ID: CAOR=d=2py-PPj_n8UEA9qR4=8G9rEPxBvHjwz8BfJwtC0o2rVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Feb 23, 2012 at 11:15 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Thu, Feb 23, 2012 at 5:20 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>
>> He's probably doing automated continuous integration testing.  Two
>> jobs ago we had a setup to do that and had 40k tests.  The whole test
>> suite took about 30 minutes to runm and kicked off automatically when
>> the last one finished and anyone touched any code.
>
> Having lots of tests is a good thing. Bring 'em on.
>
> If you use SQLite for that, then it all runs in a single thread and it
> could easily take 30 minutes or longer.
>
> Now all you have to do is parallelise the tests and everything can
> work 10 times quicker and it would be much faster than the time SQLite
> produced.

It's funny how once you start thinking of how to optimize to run 8 or
16 or more concurrent tests, you sometimes forget that doing that same
thing to some simpler tools might result in very poor performance til
you have to run the tests on the old system and start wondering why
you ever thought it was fast.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dmytrii Nagirniak 2012-02-23 23:48:58 Re: Optimise PostgreSQL for fast testing
Previous Message Merlin Moncure 2012-02-23 22:58:01 Re: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8