This makes it _much_ faster.

Also you can say AP_FETCH_MEMO_KEEP=1 to make it reuse old
information, which is useful for making comparisons.

For a further speed improvement, one can use `eatmydata'.  This is not
the default because it risks corruption of `standalone.db' which is
used for other purposes too.  Add a comment about possibly improving
this.

Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
Acked-by: Ian Campbell <ian.campb...@citrix.com>
---
 standalone-generate-dump-flight-runvars |   11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/standalone-generate-dump-flight-runvars 
b/standalone-generate-dump-flight-runvars
index 4405720..ed94792 100755
--- a/standalone-generate-dump-flight-runvars
+++ b/standalone-generate-dump-flight-runvars
@@ -36,6 +36,17 @@ if [ $# = 0 ]; then
    set `./mg-list-all-branches`
 fi
 
+if [ "x$AP_FETCH_MEMO_KEEP" = x ]; then
+       rm -rf tmp/apmemo
+       mkdir tmp/apmemo
+fi
+export AP_FETCH_PFX='./memoise tmp/apmemo'
+
+# In the future it might be nice for this script to arrange to use a
+# separate standalone.db, in tmp/ probably, for each different branch.
+# That would avoid a lot of needless write contention over the single
+# db, and make it possible to use `eatmydata' if it is installed.
+
 perbranch () {
     log=tmp/make-flight.$branch.log
     flight=check_${branch//[-._]/_}
-- 
1.7.10.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to