Re: [boost] [Bug Sprint] The November bug sprint starts tomorrow!

Subject: Re: [boost] [Bug Sprint] The November bug sprint starts tomorrow!
From: Jim Bell (Jim_at_[hidden])
Date: 2010-11-28 08:45:26

On 1:59 PM, Dean Michael Berris wrote:
> On Sat, Nov 27, 2010 at 6:25 AM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>> On 11/26/2010 4:09 PM, Klaim wrote:
>>> not sure if it's a revelant information but I tried the firs link and got
>>> a
>>> server error with this reason : "OperationalError: database is locked"
>>>
>>> I just retried and it work correctly now.
>> Yes, I'm aware of, and trying to fix, that problem. It's intermittent, but
>> recurring with sufficient propensity to be really annoying :-(
>>
> This is inherent in SQLite because it's designed to be a
> single-threaded embedded database. If there's an option to use BDB,
> PostgreSQL, or MySQL as the backing store, we can avoid this database
> locking issue.

Can we tune SQLite?

I've found big performance improvements with some of these pragmas...
PRAGMA journal_mode = OFF;
PRAGMA synchronous = OFF;
PRAGMA cache_size = 20000;
PRAGMA locking_mode = EXCLUSIVE;
PRAGMA temp_store = MEMORY;

You have to have enough control to run them every time the library
initializes. And, of course, understand their consequences.
<http://sqlite.org/pragma.html>