I work for Pluck, we handle social media integration for the NFL (Comments, Ratings, Etc.) We actually handled about 2k rps at the LB with about 10 servers taking up to 300 rps. We have a setup that does not require a centralized server over our 300 some customers (This solution was inherited from people that did not expect to server this much traffic). For our high traffic widgets, we are synchronizing in memory databases with ones on disk, (I'm the one that filed the Sqlite Backup API Ticket.. Actually just merged that code in and found the access violations.)
Your fix looks a lot better than global mutexes. If you don't mind explaining since it's not obvious to me, what caused the race condition? Alex -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Joe Mistachkin Sent: Monday, April 30, 2012 12:29 PM To: 'General Discussion of SQLite Database' Subject: Re: [sqlite] System.Data.SQLite and pooling problem Joe Mistachkin wrote: > > Alexander Spence wrote: > > > > 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. > Further analysis and testing reveals a potential race condition when using the connection pool with that static lock removed (i.e. this may be causing the access violation you are seeing); however, the static lock itself is actually not a good solution to this issue. See my candidate fix for this issue here: https://system.data.sqlite.org/index.html/ci/0ed439a5e7?sbs=0 -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Demand Media, Inc. Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
