Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #61973 > unrolled thread

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

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

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

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

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web