Rev 48: Setting _fetch_order='topological' gives sub-optimal ordering for gc=>gc fetches. in http://bazaar.launchpad.net/%7Ebzr/bzr-groupcompress/trunk

[John Arbash Meinel]

At http://bazaar.launchpad.net/%7Ebzr/bzr-groupcompress/trunk

------------------------------------------------------------
revno: 48
revision-id: john at arbash-meinel.com-20090225230422-4oigw03k7fq62eyb
parent: john at arbash-meinel.com-20090225225958-jnsftmx4zcmmlo2a
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: trunk
timestamp: Wed 2009-02-25 17:04:22 -0600
message:
  Setting _fetch_order='topological' gives sub-optimal ordering for gc=>gc fetches.
  This is because the 'autopack' code will convert to 'gc-optimal',
  which means that 'unordered' will then continue the 'gc-optimal' route.
-------------- next part --------------
=== modified file 'repofmt.py'
--- a/repofmt.py	2009-02-25 22:59:58 +0000
+++ b/repofmt.py	2009-02-25 23:04:22 +0000
@@ -405,7 +405,7 @@
         #       because the source can be smart about extracting multiple
         #       in-a-row (and sharing strings). Topological is better for
         #       remote, because we access less data.
-        self._fetch_order = 'topological'
+        self._fetch_order = 'unordered'
         self._fetch_gc_optimal = True
         self._fetch_uses_deltas = False
 
@@ -469,7 +469,7 @@
             self._reconcile_does_inventory_gc = True
             self._reconcile_fixes_text_parents = True
             self._reconcile_backsup_inventory = False
-            self._fetch_order = 'topological'
+            self._fetch_order = 'unordered'
             self._fetch_gc_optimal = True
             self._fetch_uses_deltas = False