The delay seems to coincide with the journal file creation-- it happens after our first (committed but not yet written to disk) write attempt to the database, the journal file does not at-the-time exist, and there are 500+ inserts pending with reads rapidly being added after that.
Although I too have seen anti-virus programs hose things up, we don't have any running. It was a good thing to check for though. We can live with this minor start-up penalty because our users will oftentimes run this app 12-36 hours straight and could end up hitting the database 1,000,000 times in that period. It does not appear to be any kind of error as no exceptions are thrown. We can create a minor user-appreciated perception of busyness on-screen. :-) Tom ---------------------------------------- From: [EMAIL PROTECTED] Sent: Monday, December 19, 2005 8:59 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] multiple Db's and journal file time hit? [EMAIL PROTECTED] wrote: > > We just noticed a 30-40 second hit at early on in our program running. > Others have reported things like this caused by anti-virus software running on the same machine and insisting on doing some kind of virus scan the first time the journal file is created. -- D. Richard Hipp
