Karthi M wrote:
> "Internally SQLite uses locks to serialize calls by multiple threads."
> if this is case then how can we achieve concurrency?
In general, SQLite serializes accesses to the same connection object.
To get higher concurrency (for reading), use multiple connections.
Regards,
C
On 8 Sep 2017, at 10:23am, Karthi M wrote:
>Thanks for the Reply..
>"Internally SQLite uses locks to serialize calls by multiple threads."
> if this is case then how can we achieve concurrency?
>we are using 50 threads and 1500 time it is called for 30min.
When making a change (COM
HI
Thanks for the Reply..
"Internally SQLite uses locks to serialize calls by multiple threads."
if this is case then how can we achieve concurrency?
we are using 50 threads and 1500 time it is called for 30min. At
initial stage it works fine at some point of time the performance degra
> On Sep 4, 2017, at 7:22 AM, Senthil Kumar Chellappan
> wrote:
>
> I am using only select operation ,but it gets degreaded(response time) when
> i calls the API thur multi threading
Internally SQLite uses locks to serialize calls by multiple threads. If
multiple threads are trying to access
Hi All,
I am using the SQLite version 3.20 .
I have created the inmemory database with shared cachemode as shown below
"FullUri=file::memory:?cache=shared;PRAGMA locking_mode = NORMAL;Read
Only=True;Pooling=True;Max Pool Size=120"
I am using only select operation ,but it gets degreaded(respon
5 matches
Mail list logo