From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(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 18:15:34 |
Message-ID: | CA+U5nMKNom+Z_KT8Jjj3EbeDwQY8iL5Wko_4MB2B9OtZVHy78w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
So using PostgreSQL for testing would be both quicker and more
accurate, if you set the tests up right.
The PostgreSQL regression tests are parallelised - if they weren't
we'd produce a lot less work
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Willem Buitendyk | 2012-02-23 19:18:46 | Upgrade to 9.1 causing function problem |
Previous Message | Carlos Oliva | 2012-02-23 17:33:56 | Re: Dynamic File Name for COPY TO in Stored Procedure |