Hi! Tobias Geerinckx-Rice writes: > On 21/03/17 16:32, dian_cecht@zoho.com wrote: >> Unless mirror.hydra randomly loses data in it's cache from hydra, it >> won't be random in the least. > > It will. Whether one is first to download from the cache after the > substitute is built is essentially random. > >> Quite frankly I'd like someone else to take a look at this bug, > > Glad you agree. > >> if for no other reason than I'm not sure if we're communicating clearly >> with each other here. Most of what you are saying makes no sense >> whatsoever and seems to miss the point I have attempted to make. > > I assure you it does not. > > Kind regards, > > T G-R Please allow me to jump in and voice my opinion here. To me it doesn't make sense to concern the Guix client with implementation details of how the caching of substitutes happen and its impacts. This situation is bound to change in the future or become irrelevant (say, if a new build farm would be able to sustain higher transfer speeds to the cache mirror), or if the caching implementation changes. If the current cache building implementation is slow to the point of being a problem it should be fixed (or documented). Cheers, Maxim