Thom Ericson wrote:
Marian Olteanu wrote:
You should embed the inserts into a transaction. Otherwise every
insert is a
separate ACID transaction = 2 disk spins.
I thought putting 128 of the inserts between "BEGIN;" and "COMMIT;"
did that. Am I confused?
Thom,
You are corr
> You should embed the inserts into a transaction. Otherwise every insert
> is a
> separate ACID transaction = 2 disk spins.
>
>
> I thought putting 128 of the inserts between "BEGIN;" and "COMMIT;" did
> that. Am I confused?
No, what you did was correct.
Just for grins:
If you have a
See in-line comments below
--
Jay Sprenkle wrote:
Did you put an index on the table/columns the select uses to lookup
the rowids of the parents?
I though that was what declaring 'str' as KEY and 'parent' as KEY was
supposed to do, but see Dennis Cote's resp
Thom Ericson wrote:
I am trying to pick a light weight database for a project. SQLite, on
paper, seems like the right choice, but performance is rather
disappointing. I hope it is just that I am doing something wrong.
I have built SQLite for Solaris and Win32 environments and I get
essentiall
You should embed the inserts into a transaction. Otherwise every insert is a
separate ACID transaction = 2 disk spins.
-Original Message-
From: Thom Ericson [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 10:18 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] Slow performance - U
Thom Ericson wrote:
I had hoped to be able to handle 180,000,000 rows in my largest
installation (that's gonna take a
while). Any hints from anyone
IMHO 180 mln rows is no small deal even for a big database - especially
considering you have got text column in it.
If you are trying to
On 4/6/06, Thom Ericson <[EMAIL PROTECTED]> wrote:
> I am trying to pick a light weight database for a project. SQLite, on
> paper, seems like the right choice, but performance is rather
> disappointing. I hope it is just that I am doing something wrong.
>
> I have built SQLite for Solaris and Wi
7 matches
Mail list logo
