-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014/12/17 11:09 PM, Timothy Pearson wrote:
Give it a couple weeks to mirror. Right now we are having some issues with our primary mirror (see the threads by Mike Bird on this list), and the financial state of the project cannot support a high bandwidth to upload them faster.
This is not a "polemic" mail. Just want to raise awareness.
Understood.
I have been trying to test updating from 3.5.13.2 to R14.0.0 over the last 3 days, but the package download speed has been *ridiculously* slow for several big packages (like tdelibs for example), something like 821 B/s or 1109 B/s just to give some numbers. Not to mention the amount of timeouts I received. I understand the financial situation of the project (so the absence of any type of polemic complaint), but we are definitely not doing any good to us with this situation. Potential new users may just turn away when they try to download Trinity. IMO, in the future we must make sure that a package-wise fully updated mirror system is working properly before announcing the next release.
Our primary mirrorservice.org mirror *was* working a couple days before release as far as I could tell. Then it just stopped downloading R14 packages and started re-downloading the CD images--it still hasn't gotten around to downloading the remaining R14 packages. In addition it downloads each file at least twice, sometimes more. As a result of these issues I am looking to replace the primary mirror.
The mirroring architecture is such that our primary mirror downloads directly from the TDE servers, then all secondary mirrors download from the primary. Adding additional mirrors therefore does not increase the load on the limited TDE server uplink.
Tim