[bitbake-devel] [PATCH 09/16] prserv: Use a memory journal
Mark Hatle
mark.hatle at windriver.com
Fri Aug 2 15:30:36 UTC 2019
On 8/2/19 10:20 AM, Richard Purdie wrote:
> We've seen PR Server timeouts on the autobuilder, this is likely from the
> journal being blocked on disk IO generated by the build.
>
> Since we're running with synchronous off, we may as well put the journal
> into memory and avoid any IO related stalls.
When does it flush to disk? On exit?
--Mark
> Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> ---
> lib/prserv/db.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/prserv/db.py b/lib/prserv/db.py
> index d6188a679b..117d8c052c 100644
> --- a/lib/prserv/db.py
> +++ b/lib/prserv/db.py
> @@ -257,7 +257,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.connection.execute("PRAGMA journal_mode = MEMORY;")
> self._tables={}
>
> def disconnect(self):
>
More information about the bitbake-devel
mailing list