Also possible, maybe even likely, is the user's anti-virus software is scanning the DB file when the app is first opened. 35MB is a big file for A-V to have to scan.
You or they may be able to configure the A-V to ignore the DB file. -Clark ----- Original Message ---- From: Geoff Simonds <[EMAIL PROTECTED]> To: sqlite-users@sqlite.org Sent: Thursday, January 19, 2006 7:52:55 AM Subject: Re: [sqlite] Slow query after reboot My table contains about 500,000 rows and 4 columns, not all that much data. The overall size of the db file is 35 mb. Does 15 - 20 seconds sound right to load from disk into memory? Robert Simpson wrote: > ----- Original Message ----- From: "Geoff Simonds" <[EMAIL PROTECTED]> > >> > >> The app is running on Windows XP machines and I assume that disk >> files are cached. The strange thing is that the time it takes for >> the initial read into RAM after install and first use is >> significantly shorter than after a reboot. For example, if you just >> installed the app and start it, the first time you do a query you see >> results in about 2 seconds. Subsequent queries come back much almost >> instantaneously. If the user reboots the machine or waits until the >> next day and performs the same query, it now takes about 15 seconds. >> After the 15 seconds, results come back and subsequent queries are >> instantaneous. I am not sure if this has anything to do with it but >> the app is a Deskband that lives in the taskbar on windows. > > > > That's not so strange, really. When the app is installed (along with > the database), the Windows disk cache probably has at least part of > the database file cached -- afterall it just got finished writing it. > > Robert > > > > >
