summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2019-07-24 14:12:05 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-08-06 11:21:31 +0100
commit94d5c61c9afd286e15f6ccd7b7b9e695bfcb0f97 (patch)
treec58cb7c60ce47c536049000b204c340b329d7b09 /bitbake
parentf9f308250a2d77afbf3c5db6eed889bfdab99948 (diff)
downloadpoky-94d5c61c9afd286e15f6ccd7b7b9e695bfcb0f97.tar.gz
bitbake: prserv: Use a memory journal
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. (Bitbake rev: ee3fc6030e653f3244b065fc89aafd2a7c36ae04) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/lib/prserv/db.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/lib/prserv/db.py b/bitbake/lib/prserv/db.py
index d6188a679b..117d8c052c 100644
--- a/bitbake/lib/prserv/db.py
+++ b/bitbake/lib/prserv/db.py
@@ -257,7 +257,7 @@ class PRData(object):
257 self.connection=sqlite3.connect(self.filename, isolation_level="EXCLUSIVE", check_same_thread = False) 257 self.connection=sqlite3.connect(self.filename, isolation_level="EXCLUSIVE", check_same_thread = False)
258 self.connection.row_factory=sqlite3.Row 258 self.connection.row_factory=sqlite3.Row
259 self.connection.execute("pragma synchronous = off;") 259 self.connection.execute("pragma synchronous = off;")
260 self.connection.execute("PRAGMA journal_mode = WAL;") 260 self.connection.execute("PRAGMA journal_mode = MEMORY;")
261 self._tables={} 261 self._tables={}
262 262
263 def disconnect(self): 263 def disconnect(self):