From: Phlip <phlip_cpp@...>
Date: 2005-01-11T00:06:27+09:00
Subject: Re: Tutorial: TDD for sqlite3-ruby

Jamis Buck wrote:

> This is a very important point, and I'd like to stress it. SQLite3, in
> particular, behaves _very poorly_ unless you use explicit
> transactions. In my testing and benchmarking, I've seen inserts take
> _orders of magnitude_ longer to execute outside of an explicit
> transaction, mostly due to disk activity (from reading and writing
> journals, I imagine).

So if I write a bunch of test cases, and if setup() erased the database and
built it again (unpopulated), then how much of the performance hit was from
rebuilding the database (with 4 simple tables), and how much was from the
lack of transactions?

My bad for not profiling, and just assuming it was the rebuilding!

-- 
  Phlip
  http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces