Groups > comp.lang.python > #61973

Re: Is it more CPU-efficient to read/write config file or read/write sqlite database?

References	<20131214101518.69b040dc@bigbox.christie.dr> <20131215231228.GA6608@cskk.homeip.net>
Date	2013-12-16 10:50 +1100
Subject	Re: Is it more CPU-efficient to read/write config file or read/write sqlite database?
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.4157.1387151420.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Mon, Dec 16, 2013 at 10:12 AM, Cameron Simpson <cs@zip.com.au> wrote:
>   + traditionally, sqlite is extreme fsync() happy; forces a disc
>     level flush on each commit - extremely slow on busy databases,
>     not to mention hard of drives

I'd say that's correct behaviour. A commit should be sync'd to disk.
If you don't want it to go to the disk yet, don't commit yet!

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Is it more CPU-efficient to read/write config file or read/write sqlite database? Chris Angelico <rosuav@gmail.com> - 2013-12-16 10:50 +1100

csiph-web