Alexander Spence wrote: > > I noticed this while supporting the NFL Draft, not sure exactly how many threads were > going through the score code that was causing this exception, but the servers were > generally processing 200-300 requests per second at the time. >
Just curious, were you supporting the NFL Draft in an official capacity? Also, you managed to get 200 to 300 requests per second using System.Data.SQLite (presumably also using ASP.NET)? > > One was caused by > http://system.data.sqlite.org/index.html/tktview?name=fc994d007d and the other was > fixed by this check in http://system.data.sqlite.org/index.html/info/10d400ebd0 (THANK > YOU!). > Yeah, several robustness fixes have been made in the area of resource cleanup. > > What is the purpose of these locks when Sqlite itself has been compiled as ThreadSafe? > I'm not sure what the original intent of that lock was; however, after reviewing the code, that lock does not seem to serve a useful purpose. My plan now is to remove it for the next release. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
