On 3 May 2012, at 10:30pm, Igor Tandetnik wrote:
> On 5/3/2012 5:04 PM, Marco Era wrote:
>> Now that I have some time, I'm stress testing it to see how much I can get
>> from it; what I want to check is its performance in a multithreading
>> environment.
>>
>> To my surprise, it seems that se
> Serialized test (SQLITE_THREADSAFE=1):
>
> The main thread opens the database, sets the cache and busy timeout to huge
> values and passes the db descriptor to the threads.
>
> Multithreaded test (SQLITE_THREADSAFE=2):
> The main thread creates the other threads and wait; each thread opens its o
On 5/3/2012 5:04 PM, Marco Era wrote:
Now that I have some time, I'm stress testing it to see how much I can get from
it; what I want to check is its performance in a multithreading environment.
To my surprise, it seems that serialized access to the database (which is the
default in the source
Hi there,
I've been using sqlite for a few years now and it worked fine in my experience.
Now that I have some time, I'm stress testing it to see how much I can get from
it; what I want to check is its performance in a multithreading environment.
To my surprise, it seems that serialized access
4 matches
Mail list logo