Subject: Re: [boost] [trac] Website performance, and disabling the code browser?
From: Phil Endecott (spam_from_boost_dev_at_[hidden])
Date: 2010-11-28 19:09:07
Dean Michael Berris wrote:
> On Mon, Nov 29, 2010 at 4:31 AM, Artyom <artyomtnk_at_[hidden]> wrote:
>> It is quite big misconception that DB is bottle neck.
> Sorry, but SQLite is not fast enough if you have multiple processes
> trying to perform the same query on the same database. The reason is
> because of the database locking mechanism that the SQLite library
> enforces on the database file.
My understanding was that SQLite only did locking for writes, i.e. it's
possible for multiple threads to be reading at the same time. In fact this
is FAQ #5 at http://www.sqlite.org/faq.html#q5 :
"SQLite allows multiple processes to have the database file open at
once, and for multiple processes to read the database at once. When
any process wants to write, it must lock the entire database file
for the duration of its update. But that normally only takes a few
milliseconds. Other processes just wait on the writer to finish then
continue about their business."
Is trac doing writes for things that should only be reads, perhaps?
(in another post:)
> I like the idea of disabling the code browser.
I don't; to me an occasional error message is better than not working
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk