Yes, each thread does its own sqlite3_open(). In fact, I get the same behavior when each thread is using completely separate files (for example, making multiple copies of the database, with each thread using a different copy).
-Jeff -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: Monday, October 18, 2010 11:47 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Scaling of Cache On 18 Oct 2010, at 5:25pm, Powell, Jeff wrote: > I have an application which utilizes multiple threads, each of which never > writes to the database, and none of which shares its cache. > > In pcache1Fetch, sqlite mutexes around the cache handling, which appears to > be causing significant waits/scalability issues in my application. If I > disable this mutex, the application crashes. Does each thread do a separate sqlite3_open() or are they all using the same database handle ? Simon. _______________________________________________ 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
