> -----Original Message----- > From: Maksim Yevmenkin [mailto:[EMAIL PROTECTED] > Sent: Monday, April 11, 2005 12:27 PM > To: Robert Simpson > Cc: sqlite-users@sqlite.org > Subject: Re: [sqlite] sqlite performance problem >
[snip] > i said i print these rows to /dev/null too in my perl code. plus the > perl code does some other things such as joining these rows with other > hashes and summing the numbers. That's fine. I was merely trying to account for the 50% speed difference between the two differing column tests, which has been accomplished. > > As for the temp table ... I haven't tried this, but isn't > "temp" a reserved > > word in SQLite? More importantly, you should be doing this > statement inside > > yes, it is. i really want to create 'temporary table' in memory. i was > really hoping it would speed things up. I misread the statement, so ignore me on that part. However, 339,000 rows into a temporary in-memory table ... I tried some experiments locally here and none of them took more than 2 seconds to execute. Are you sure you're not using up all available memory, which is causing the system to hit the swapfile? What does this same query look like when you drop the "temp" from the query? Robert
