On Jan 17, 2008 3:48 PM, Philip Nick <[EMAIL PROTECTED]> wrote: > Greetings, > > Currently I am using sqlite3 in a multi-process/multi-threaded server > setting.
opening a file is very slow. You need to move it out of your loop. > I have noticed my program basically reads the whole database every time the > query is run. The IO Read bytes increases by 900k for every query we run. We > also chew a good chunch of the cpu I have tried keeping the database > connection open and open/closing for every query. But there was no change. > if I launch the CLI and run the query it runs instantly and monitoring the > IO read bytes is see only ~20 bytes of read to execute the query, when my > code is using over 900k for every call. I have been looking into the CLI > source to see what is done differently, but was hoping someone on here might > have some insight. The operating system will cache files it reads in memory. If your process reads the file and then you open the CLI it will still be in memory from before and will not give you comparable times. If your process reads the whole database for every call you didn't optimize your sql. You need to create indexes to optimize your query -- The PixAddixImage Collector suite: http://groups-beta.google.com/group/pixaddix SqliteImporter and SqliteReplicator: Command line utilities for Sqlite http://www.reddawn.net/~jsprenkl/Sqlite Cthulhu Bucks! http://www.cthulhubucks.com ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
