diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-07-24 14:08:30 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-08-06 11:21:07 +0100 |
| commit | 7ae56a4d4fcf66e1da1581c70f75e30bfdf3ed83 (patch) | |
| tree | f32888989016b339b2a94985c8eddca8f5ec1a66 | |
| parent | a4fa8f1bd88995ae60e10430316fbed63d478587 (diff) | |
| download | bitbake-7ae56a4d4fcf66e1da1581c70f75e30bfdf3ed83.tar.gz | |
hashserv: Turn off sqlite synchronous mode
We're seeing performance problems with hashserv running on a normal build
system. The cause seems to be the large amounts of file IO that builds involve
blocking writes to the database. Since sqlite blocks on the sync calls, this
causes a significant problem.
Since if we lose power we have bigger problems, run with synchronous=off
to avoid locking and put the jounral into memory to avoid any write issues
there too.
This took writes from 120s down to negligible in my tests, which means
hashserv then responds promptly to requests.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | lib/hashserv/__init__.py | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/lib/hashserv/__init__.py b/lib/hashserv/__init__.py index 7ec9b6441..544bc86b1 100644 --- a/lib/hashserv/__init__.py +++ b/lib/hashserv/__init__.py @@ -21,6 +21,8 @@ class HashEquivalenceServer(BaseHTTPRequestHandler): def opendb(self): self.db = sqlite3.connect(self.dbname) self.db.row_factory = sqlite3.Row + self.db.execute("PRAGMA synchronous = OFF;") + self.db.execute("PRAGMA journal_mode = MEMORY;") def do_GET(self): try: |