Bruno Moreira Guedes wrote: > And even with too many 'locking concurrency', I've done some stress > testing and SQLite still very well. I've thrown the SQLITE_BUSY errors > to a retry algorithm, which waits a random time in a time range and > try again until a high number of retries. Using it, I've wrote a > program which writes data forever on the database, and get the data > again. So, I get to run 8 instances of this testing program and the > database seems to answer very well. But even with this tests, > something seems to be wrong for me, and I'm researching to ensure > everything will be nice on the new environment. I'll improve the > database layout for better performance too. > Hi, Bruno!
You might want to take a look at the sqlite3_busy_timeout() function in the SQLite3 C API - http://sqlite.org/c3ref/busy_timeout.html - which does exactly that and might free you from the effort of maintaining your own solution to the same problem. Hope this helps, Mihai _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
