Dave Borowitz 67700e9b90 sync: Order projects according to last fetch time
Some projects may consistently take longer to fetch than others, for
example a more active project may have many more Gerrit changes than a
less active project, which take longer to transfer. Use a simple
heuristic based on the last fetch time to fetch slower projects first,
so we do not tend to spend the end of the sync fetching a small number
of outliers.

This algorithm is probably not optimal, and due to inter-run latency
variance and Python thread scheduling, we may not even have good
estimates of a project sync time.

Change-Id: I9a463f214b3ed742e4d807c42925b62cb8b1745b
2012-10-24 14:51:58 -07:00
..
2012-10-22 12:30:14 +09:00
2012-10-22 12:30:14 +09:00
2012-10-22 12:30:14 +09:00
2012-10-22 12:30:14 +09:00
2012-09-18 09:54:57 +02:00
2012-08-23 12:15:26 +02:00
2012-10-22 12:30:14 +09:00
2012-08-23 12:15:26 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 14:29:46 -07:00
2011-03-16 12:55:44 -07:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-09-18 09:54:57 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-09-18 09:54:57 +02:00