On Friday, 21 September, 2012, @10:53, Sebastian Krysmanski said: > I wish it were like you said. However, in my understanding multiple > connections to the same database are realized by file system locks. So > switching from serialized to multi-threading mode doesn't make much > difference because the main slow down are the file system locks.
Can you try passing the SQLITE_OPEN_SHAREDCACHE and SQLITE_OPEN_NOMUTEX to the connection per thread and see how that behaves. You get the same advantage of reducing I/O and memory management by using a single page-cache, yet you now no longer have serialization (or mutexes to enforce serialization) in the library call path. If the serialization/mutex code is causing any significant performance effect, this should demonstrate it clearly. --- () ascii ribbon campaign against html e-mail /\ www.asciiribbon.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
