Re: [sqlite] multiple thread concurrency problem with exclusive transaction locks

2005-01-13 Thread Eli Burke
2. disable asserts. I don't know how this is done in C, but I assume that in a release build, asserts are off. Disable asserts() using -DNDEBUG=1. This more than doubles the speed of SQLite. Asserts() are turned off in release builds. We build sqlite3.08 as follows: ./configure

Re: [sqlite] multiple thread concurrency problem with exclusive transaction locks

2005-01-13 Thread D. Richard Hipp
mike cariotoglou wrote: 2. disable asserts. I don't know how this is done in C, but I assume that in a release build, asserts are off. Disable asserts() using -DNDEBUG=1. This more than doubles the speed of SQLite. Asserts() are turned off in release builds. -- D. Richard Hipp -- [EMAIL

RE: [sqlite] multiple thread concurrency problem with exclusive transaction locks

2005-01-12 Thread mike cariotoglou
I am not running on *ix, so I cannot test.however, your mentioning multi-cpu machines, brings something to mind. In windows, most synchronization functions rely on some form of INTERLOCKED operation. Now, these operations are implemented differently on multi-cpu (and hyperthreading counts as