Well, That certainly did the trick. Much obliged!
Rate now > 2000 inserts/second including transaction processing and 3390
inserts.
-R.
Igor Tandetnik wrote:
> Rod Dav4is wrote:
>
>> *Insert rate*: 7/sec.
>>
>
> Run batches of inserts within a single transaction. It's not the insert
> i
Thanks. I'll give it a try.
Igor Tandetnik wrote:
> Rod Dav4is wrote:
>
>> *Insert rate*: 7/sec.
>>
>
> Run batches of inserts within a single transaction. It's not the insert
> itself that's slow, it's the process of committing a transaction. By not
> starting an explicit transaction,
On Wed, Sep 09, 2009 at 06:59:18PM -0400, Rod Dav4is scratched on the wall:
> *Insert rate*: 7/sec.
http://www.sqlite.org/faq.html#q19
--
Jay A. Kreibich < J A Y @ K R E I B I.C H >
"Our opponent is an alien starship packed with atomic bombs. We have
a protractor." "I'll go home and
Hi Rod,
Regarding: *Insert rate*: 7/sec.
You'll want to wrap your INSERT loop in a transaction, i.e., BEGIN /
COMMIT.
Without a transaction, each INSERT has to wait for multiple disk
revolutions.
http://www.sqlite.org/lang_transaction.html
If you have a huge number of inserts, you may want to
Rod Dav4is wrote:
> *Insert rate*: 7/sec.
Run batches of inserts within a single transaction. It's not the insert
itself that's slow, it's the process of committing a transaction. By not
starting an explicit transaction, you commit an implict one on every
statement.
Igor Tandetnik
___
The environment:
Compaq Presario CQ60 w/Pentium dual core 2GHz+2GHz, 2GB RAM
Windows Vista Home Premium w/SP2, fully updated & patched
SQLite/3 (3.6.17)
My db 17.5Mb (small-medium size, I would say)
The table: CREATE TABLE INDI (ref text , indi text)
No indices or other
6 matches
Mail list logo
