| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dmytrii Nagirniak <dnagir(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, David Salisbury <salisbury(at)globe(dot)gov>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Optimise PostgreSQL for fast testing |
| Date: | 2012-02-24 02:19:32 |
| Message-ID: | CAOR=d=0dVEqraa9h+7C_J_COtWB897qOOsrsQmcfajNiCFBx7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 23, 2012 at 5:22 PM, Dmytrii Nagirniak <dnagir(at)gmail(dot)com> wrote:
> On 24/02/2012, at 5:15 AM, Simon Riggs wrote:
>
> 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.
>
>
> That is certainly true. And there are number of techniques to make tests
> faster.
> But that is outside of the scope of this thread I believe.
Is there a reaon why you can't parallelize your tests? If you could
run 10 or so at a time it would be worth benchmarking.
Also, look into automating your testing, so that you don't need to run
the tests all the time, they run in the background, and if something
breaks they send you an alert with the code that broke things etc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-02-24 02:33:49 | Re: Optimise PostgreSQL for fast testing |
| Previous Message | Adrian Klaver | 2012-02-24 02:04:55 | Re: Upgrade to 9.1 causing function problem |