From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] prserv: don't wait until exit to sync
Date: Tue, 04 Nov 2014 10:51:39 +0000 [thread overview]
Message-ID: <1415098299.23396.16.camel@ted> (raw)
In-Reply-To: <1415090528.23396.4.camel@ted>
On Tue, 2014-11-04 at 08:42 +0000, Richard Purdie wrote:
> We're still figuring out what is going on but it is roughly that:
>
> a) The build generates a ton of IO
> b) That IO builds up into a queue
> c) The PR service decides it needs to sync to disk
> d) The PR service hits an fsync() of some kind in sqlite whilst writing
> e) The PR service is blocked for its clients until the sync() finishes
> f) Connections to the PR service timeout.
>
> It would be nice if we could write the sqlite data in a separate thread
> whilst the readers continue. There is an asynchronous module but its
> deprecated:
>
> http://www.sqlite.org/asyncvfs.html
>
> WAL is recommended instead:
>
> http://www.sqlite.org/wal.html
>
> so we probably need to look at that.
FWIW,
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t222&id=df0dabbf90f3da7153295adb83e51c41ae4d9375
is a patch Ross is kindly testing for me...
Cheers,
Richard
next prev parent reply other threads:[~2014-11-04 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 17:27 [PATCH] prserv: don't wait until exit to sync Ben Shelton
2014-11-02 21:00 ` Burton, Ross
2014-11-03 15:47 ` Ben Shelton
2014-11-03 17:30 ` Richard Purdie
2014-11-03 18:27 ` Gary Thomas
2014-11-04 8:42 ` Richard Purdie
2014-11-04 10:51 ` Richard Purdie [this message]
2014-11-04 13:10 ` Burton, Ross
2014-11-04 14:13 ` Richard Purdie
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=1415098299.23396.16.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=gary@mlbassoc.com \
/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