Wayne Bradney wrote:
Howard,Thanks for the links - mdb/sqlightning looks interesting.Before I
dive in, however:1. As I understand it, sqlightning is a drop-in replacement
for SQLite.Interop.dll, and I can still use System.Data.SQLite as my
high-level interface?
Right.
2. Is there a compiled re
ers@sqlite.org
> Subject: Re: [sqlite] Concurrent read performance
>
> Wayne Bradney wrote:
> >>> All access in SQLite is serialized. Apologies if I'm missing something
> >>> fundamental here, but that's not what I'm seeing with a file-backed
>
s. More info here
http://symas.com/mdb/
and SQLite ported to use MDB as its backend is available here
https://gitorious.org/mdb/sqlightning
Date: Sat, 12 Jan 2013 17:48:56 +0000
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Concurrent read performance
On 12 Jan 2013, at 5:38pm, Wayne Bra
---
() ascii ribbon campaign against html e-mail
/\ www.asciiribbon.org
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Wayne Bradney
> Sent: Saturday, 12 January, 2013 14:37
> To: General Discussion of SQLite Datab
eries still appear to
be serialized. Would this approach require SQLITE_CONFIG_MULTITHREAD or
SQLITE_OPEN_NOMUTEX, I wonder?
> Date: Sat, 12 Jan 2013 13:39:35 -0700
> From: kmedc...@dessus.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Concurrent read performance
>
>
e.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Wayne Bradney
> Sent: Saturday, 12 January, 2013 12:36
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Concurrent read performance
>
> Increasing cache_size didn't seem to have an effect. I think I&#
put on what our options might be in terms of SQLite configuration of
> memory-backed databases. > From: slav...@bigfraud.org
>> Date: Sat, 12 Jan 2013 17:48:56 +
>> To: sqlite-users@sqlite.org
>> Subject: Re: [sqlite] Concurrent read performance
>>
>>
>> On
Bradney
> Sent: Saturday, January 12, 2013 11:39 AM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] Concurrent read performance
>
> I have a requirement for which I'm proposing SQLite as a solution, and would
> appreciate some feedback to clarify my thinking. The applica
ation was that we could achieve this with SQLite, but were surprised by
the apparent lack of read-concurrency, and wanted to get some input on what our
options might be in terms of SQLite configuration of memory-backed databases. >
From: slav...@bigfraud.org
> Date: Sat, 12 Jan 2013 17:48
read_uncommitted didn't seem to have any effect
> From: mdblac...@yahoo.com
> To: sqlite-users@sqlite.org
> Date: Sat, 12 Jan 2013 11:47:55 -0600
> Subject: Re: [sqlite] Concurrent read performance
>
> Did you try read-uncommitted?
> Sounds promising...
>
&g
Wayne Bradney wrote:
> 1. when shared cache is enabled, all reads are serialized,
Yes.
> I guess I MUST use a file-backed database to get concurrent reads,
> even though I don't need the persistence and don't want to take the
> I/O hit.
If the in-memory database works, you do have enough memory
] Concurrent read performance
I have a requirement for which I'm proposing SQLite as a solution, and would
appreciate some feedback to clarify my thinking. The application is a shared
service (.NET/WCF) that caches relational data in-memory and serves it up
when (read-only) requests come in
On 12 Jan 2013, at 5:38pm, Wayne Bradney wrote:
> "mode=memory&cache=shared"
> 1. when shared cache is enabled, all reads are serialized, and
All access in SQLite is serialised. All transactions require locking the
entire database. SQLite is very simple -- 'lite' -- so queries run extremel
AM
To: sqlite-users@sqlite.org
Subject: [sqlite] Concurrent read performance
I have a requirement for which I'm proposing SQLite as a solution, and would
appreciate some feedback to clarify my thinking. The application is a shared
service (.NET/WCF) that caches relational data in-memory and s
I have a requirement for which I'm proposing SQLite as a solution, and would
appreciate some feedback to clarify my thinking. The application is a shared
service (.NET/WCF) that caches relational data in-memory and serves it up when
(read-only) requests come in (via operation contracts) from mul
15 matches
Mail list logo
