Re: [Imdbpy-devel] [Imdbpy-help] Timing SQLITE creation

2009-01-15 Thread dalgoda
On 1/14/09, Davide Alberani wrote: > Not exactly (actually, at least); the only information saved and > restored between two runs are "imdbID" (collected when IMDbPY have > to retrieve from the web the "real" imdbID for a movie/person/..., > and stored in the database for future faster accesses).

Re: [Imdbpy-devel] [Imdbpy-help] Timing SQLITE creation

2009-01-14 Thread Davide Alberani
On Jan 13, Mike Castle wrote: > I also just tested with PRAGMA journal_mode = OFF; Good - I'll update the code and documentation ASAP (and submit it to you, to check that I've understood everything). > But, are you doing something at the beginning with preserving current > ids? Not exactly (ac

Re: [Imdbpy-devel] [Imdbpy-help] Timing SQLITE creation

2009-01-13 Thread Mike Castle
I also just tested with PRAGMA journal_mode = OFF; and, while it did prevent sqlite from making and removing journal files all the time, it turns out that it didn't make any significant difference. The measurement was actually 5 minutes slow, considering the variability of the machine, probably me

Re: [Imdbpy-devel] [Imdbpy-help] Timing SQLITE creation

2009-01-13 Thread Davide Alberani
On Jan 13, Mike Castle wrote: > First, I remembered to build the DB on a file system that is NOT > journaled. This actually got me to a time similar to above. [...] > (I knew this of course, I'd never thought that the difference would be _that_ huge. That's for sure a thing that must be docum