Hello Drew, Why multiple threads? What kind of performance do you get if you only use a single thread?
Is it one thread per database perhaps? C Tuesday, August 9, 2011, 4:46:13 PM, you wrote: DK> We have an application that does not scale well especially 8 and 16 DK> threads we are getting about 10% at best to -50% at worst (2 and 4 are okay DK> aprox. 40-50%). DK> We have narrowed the problem down to the SQLite code. DK> Looking for best practices from anyone that overcame scaling issues. DK> First we generate 35 different SQLite databases, this is done in a separate DK> program and performance is not an issue. DK> The application is a C++ app. that accesses all the databases in a read DK> only style. Size of database range from 1MB to 10GB. DK> Each thread does the following in a loop DK> 1. Grab a record from an external system (not SQLite) DK> 2. Runs several SQLite queries to process the record DK> We are currently using 3.6.14 (has this been improved in new versions?) DK> Is there any compile time options or pragma's that are specifically DK> engineered at optimizing for read only and/or scaling? DK> Thank you in advance, DK> Drew DK> _______________________________________________ DK> sqlite-users mailing list DK> sqlite-users@sqlite.org DK> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Best regards, Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
