Hi,
On Saturday 12 December 2009 00:59:13 Scott Marlowe wrote:
> On Fri, Dec 11, 2009 at 3:52 PM, Michael Clemmons
> > Createdb takes
> > 12secs on my system(9.10 pg8.4 and ext4) which is impossibly slow for
> > running 200unittests.
> > Fsync got it to .2secs or so which is blazing but
> > als
On Fri, Dec 11, 2009 at 3:52 PM, Michael Clemmons
wrote:
> Thanks all this has been a good help.
> I don't have control(or easy control) over unit tests creating/deleting
> databases since Im using the django framework for this job.
Reminds of the issues we had with Ruby on Rails and it's (at the
Thanks all this has been a good help.
I don't have control(or easy control) over unit tests creating/deleting
databases since Im using the django framework for this job. Createdb takes
12secs on my system(9.10 pg8.4 and ext4) which is impossibly slow for
running 200unittests. Fsync got it to .2s
Scott Mead wrote:
The other common issue is that developers running with something like
'fsync=off' means that they have completely unrealistic expectations
of the performance surrounding something.
Right, but the flip side here is that often the production server will
have hardware such as a c
On Fri, Dec 11, 2009 at 3:12 PM, Scott Carey wrote:
>
> On 12/11/09 1:57 PM, "Scott Marlowe" wrote:
>
>>
>> This is my big issue. dropping / creating databases for unit tests is
>> overkill. Running any DDL at all for a unit test seems wrong to me
>> too. Insert a row if you need it, MAYBE. U
On 12/11/09 1:57 PM, "Scott Marlowe" wrote:
>
> This is my big issue. dropping / creating databases for unit tests is
> overkill. Running any DDL at all for a unit test seems wrong to me
> too. Insert a row if you need it, MAYBE. Unit tests should work with
> a test database that HAS the st
On Fri, Dec 11, 2009 at 2:59 PM, Scott Mead
wrote:
> On Fri, Dec 11, 2009 at 4:39 PM, Nikolas Everett wrote:
>>
>>
>>
>> Fair enough. I'm of the opinion that developers need to have their unit
>> tests run fast. If they aren't fast then your just not going to test as
>> much as you should. If
On Fri, Dec 11, 2009 at 4:39 PM, Nikolas Everett wrote:
>
>
>
> Fair enough. I'm of the opinion that developers need to have their unit
> tests run fast. If they aren't fast then your just not going to test as
> much as you should. If your unit tests *have* to createdb then you have to
> do wh
On Fri, Dec 11, 2009 at 2:39 PM, Nikolas Everett wrote:
>
>
> On Fri, Dec 11, 2009 at 3:50 PM, Joshua D. Drake
> wrote:
>>
>> On Fri, 2009-12-11 at 15:43 -0500, Nikolas Everett wrote:
>> > Turning fsync off on a dev database is a bad idea? Sure you might
>> > kill it and have to start over, but
On Fri, Dec 11, 2009 at 3:50 PM, Joshua D. Drake wrote:
> On Fri, 2009-12-11 at 15:43 -0500, Nikolas Everett wrote:
> > Turning fsync off on a dev database is a bad idea? Sure you might
> > kill it and have to start over, but thats kind of the point in a dev
> > database.
>
> My experience is tha
On Fri, 2009-12-11 at 15:43 -0500, Nikolas Everett wrote:
> Turning fsync off on a dev database is a bad idea? Sure you might
> kill it and have to start over, but thats kind of the point in a dev
> database.
My experience is that bad dev practices turn into bad production
practices, whether inte
Turning fsync off on a dev database is a bad idea? Sure you might kill it
and have to start over, but thats kind of the point in a dev database.
On Fri, Dec 11, 2009 at 12:58 PM, Joshua D. Drake wrote:
> On Thu, 2009-12-10 at 20:38 -0500, Nikolas Everett wrote:
> > In my limited experience ext4
On Thu, 2009-12-10 at 20:38 -0500, Nikolas Everett wrote:
> In my limited experience ext4 as presented by Karmic is not db
> friendly. I had to carve my swap partition into a swap partition and
> an xfs partition to get better db performance. Try fsync=off first,
> but if that doesn't work then t
13 matches
Mail list logo
