From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] prserv: Use WAL mode
Date: Thu, 6 Nov 2014 14:58:11 +0100 [thread overview]
Message-ID: <20141106135811.GA2455@jama> (raw)
In-Reply-To: <1415206693.23396.56.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
On Wed, Nov 05, 2014 at 04:58:13PM +0000, Richard Purdie wrote:
> Ideally, we want the PR service to have minimal influence from
> queued disk IO. sqlite tends to be paranoid about data loss and
> locks/fsync calls. There is a "WAL mode" which changes the journalling
> mechanism and would appear much better suited to our use case.
>
> This patch therefore switches the database to what WAL mode. With this
^ what = that?
> change, write overhead appears significantly reduced.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/bitbake/lib/prserv/db.py b/bitbake/lib/prserv/db.py
> index 3bdc046..9d6d115 100644
> --- a/bitbake/lib/prserv/db.py
> +++ b/bitbake/lib/prserv/db.py
> @@ -235,6 +235,7 @@ class PRData(object):
> self.connection=sqlite3.connect(self.filename, isolation_level="EXCLUSIVE", check_same_thread = False)
> self.connection.row_factory=sqlite3.Row
> self.connection.execute("pragma synchronous = off;")
> + self.connection.execute("PRAGMA journal_mode = WAL;")
> self._tables={}
>
> def __del__(self):
>
>
> --
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-11-06 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 16:58 [PATCH] prserv: Use WAL mode Richard Purdie
2014-11-06 13:58 ` Martin Jansa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141106135811.GA2455@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox