the hard disk is shared so it is a critical resource,as well as 100 processes doesn't seem realistic on a single processor, dual core or not.
so I can understand your result, I find even them not too bad ... Cheers, Sylvain On Thu, May 28, 2009 at 12:38 AM, zhrahman <rahman_zao...@yahoo.com> wrote: > > I am doing a simple test on sqlite where in step one, I just write 10,000 > records on a simple database having three fileds. In step 2, after the > write > is done, I want 100 process reading from the database and doing simple > SQLs, no update on the databse just simple select read operations. I am > getting horrible performance when I increase the number of processes. Now > each process only opens the database connection in read only mode. Still I > am guessing some lock is placed on the database and that why even the read > operation is slowing down drastically with the increase of the number of > processes. Any idea what I need to do to boost performance? For 100 > processes doing reads it takes like 10 seconds to do 10000 SQL by each > process. If I reduce the number of processes from 1000 to 1 it only > finishes > in a second > -- > View this message in context: > http://www.nabble.com/SQlite-performance-on-multi-process-env-tp23752056p23752056.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
