Dave Borowitz d947858325 sync: Keep a moving average of last fetch times
Try to more accurately estimate which projects take the longest to
sync by keeping an exponentially weighted moving average (a=0.5) of
fetch times, rather than just recording the last observation. This
should discount individual outliers (e.g. an unusually large project
update) and hopefully allow truly slow repos to bubble to the top.

Change-Id: I72b2508cb1266e8a19cf15b616d8a7fc08098cb3
2012-10-24 14:52:07 -07:00
2009-06-02 00:09:07 +02:00
2009-06-02 00:09:07 +02:00
2012-10-09 12:45:30 +02:00
2012-10-22 12:30:14 +09:00
2008-10-21 07:00:00 -07:00
2012-10-22 12:30:14 +09:00
2012-10-10 08:30:15 +02:00
2012-10-09 12:45:30 +02:00
2012-10-09 12:45:30 +02:00
2012-10-22 12:30:14 +09:00
2012-10-22 12:30:14 +09:00
2012-10-09 12:45:30 +02:00
2011-09-19 14:52:57 -07:00
2012-10-22 12:30:14 +09:00
2012-10-10 08:30:15 +02:00
Description
No description provided
Apache-2.0 35 MiB
Languages
Python 99.1%
Shell 0.9%