1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
-
+
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
|
Road Map
--------
Note 1: This road-map is still evolving and subject to change without notice.
RFC
~~~
*Purpose*: shrink megatest.db data to enable lower load and higher performance.
Method: add a completed-runs.db and automatically move runs data from megatest.db to that db
*Method*: add a completed-runs.db and automatically move runs data from megatest.db to that db
Design:
• completed-runs.db is a full megatest database with complete schema
• the data move would involve these steps
1. copy the run data to completed-runs.db
2. remove the run data, first from /tmp/…/megatest.db and /tmp/…/megatest_ref.db, followed by megatest.db
• accessing the data would be unchanged for most operations.
• a mode -full-db will be added which when specified would attach the completed-runs.db to megatest.db before doing the query
• mechanisms for moving runs to/from the megatest.db would be added
o -reduce-records => move runs to completed-runs.db
o -restore-records => move runs from completed-runs.db to megatest.db
*Design*:
. completed-runs.db is a full megatest database with complete schema
. the data move would involve these steps
.. copy the run data to completed-runs.db
.. remove the run data, first from /tmp/…/megatest.db and /tmp/…/megatest_ref.db, followed by megatest.db
. accessing the data would be unchanged for most operations.
. a mode -full-db will be added which when specified would attach the completed-runs.db to megatest.db before doing the query
. mechanisms for moving runs to/from the megatest.db would be added
.. -reduce-records => move runs to completed-runs.db
.. -restore-records => move runs from completed-runs.db to megatest.db
Branch: This work is taking place on branch v1.65-reduce-records
Requests for comment.
Architecture Refactor
|