On 5/18/06, Brannon King <[EMAIL PROTECTED]> wrote:
>Also, do a large number of inserts within a transaction. (1000-100,000 or
so, not a billion ;) )
I don't see how increasing the number of inserts per transaction changes the
speed at which the sqlite3_step function executes when it is called on an
insert in the middle of the transaction. I'll put some more commentary on
that in my next response to Dennis.
Each tiime you complete a transaction it waits for the OS to flush the
data to the
disk. The system has to wait for the drive platter to rotate to the
correct position
before writing. Optimal write speed would be to queue as many records as you
can in the time it takes for one disk platter rotation. Optimal overall time
would be minimizing the overhead of disk flushes. You have
memory limitations though. Most systems will not let you queue a billion
operations in RAM.
