I was actually wondering about this part too.  You would need quite a few machines downstream of your local mirror to make up the difference switching from cdiffs for each machine to CVD's, at least given the current size of daily.cvd.  It probably is about time for us to fold daily into main, and start fresh with a smaller daily.

I do want to say, since I'm not sure I've said it before, thank-you to everyone who is making an effort to reduce bandwidth usage.  Despite being a part of a huge corporation - we are an open source project that doesn't have a subscription service or anything to make money for the company.  As a result, we have very limited funds year to year and your efforts do make a difference.  Thanks!

-Micah


On Dec 15, 2018, at 10:14 AM, J.R. <themadbeaker@gmail.com> wrote:

Third... Have you done a cost-benefit analysis? I know you said you
wanted to help reduce bandwidth, but when you are downloading the
entire daily.cvd file each time there is an update, that's currently a
little over 50MB each update. I downloaded the last 10 cdiff files and
they look to average about 15k... So by that math (I'm still drinking
my coffee this morning, so I could be wildly wrong)... You would need
to have over 3,333 machines to be saving any bandwidth...