Index: rmt.scm
==================================================================
--- rmt.scm
+++ rmt.scm
@@ -206,11 +206,11 @@
       (if (not (member cmd api:read-only-queries))
 	  (let ((start-time (current-seconds)))
 	    (mutex-lock! *db-multi-sync-mutex*)
 	    ;; (if (not (hash-table-ref/default *db-local-sync* run-id #f))
 	    ;; just set it every time. Is a write more expensive than a read and does it matter?
-	    (hash-table-set! *db-local-sync* run-id start-time) ;; the oldest "write"
+	    (hash-table-set! *db-local-sync* (or run-id 0) start-time) ;; the oldest "write"
 	    (mutex-unlock! *db-multi-sync-mutex*)))
       res)))
 
 (define (rmt:send-receive-no-auto-client-setup connection-info cmd run-id params)
   (let* ((run-id   (if run-id run-id 0))

Index: tests/fullrun/megatest.config
==================================================================
--- tests/fullrun/megatest.config
+++ tests/fullrun/megatest.config
@@ -61,11 +61,11 @@
 # or for hard links
 
 # testcopycmd cp --remove-destination -rlv TEST_SRC_PATH/. TEST_TARG_PATH/.
 
 # FULL or 2, NORMAL or 1, OFF or 0
-# synchronous 1
+synchronous 0
 # Throttle roughly scales the db access milliseconds to seconds delay
 throttle 0.2
 # Max retries allows megatest to re-check that a tests status has changed
 # as tests can have transient FAIL status occasionally
 maxretries 20
@@ -135,11 +135,14 @@
 # Three minutes is 0.05 hours
 # timeout 0.025
 timeout 0.01
 
 # Server is required - slower but more resistant to Sqlite issues.
-required yes
+# required yes
+
+# Start server when average query takes longer than this
+server-query-threshold -1
 
 # daemonize yes
 # hostname #{scheme (get-host-name)}
 
 ## disks are: