 |
Installer only downloads configuration files and manifests from the main server. That very little traffic: something like 20 MB on fresh install of 2.09 release, and almost nothing on subsequent runs. This is enforced for security reasons. As for the main downloads, they are taken from randomly chosen mirrors. The mirrors are weighted by probability, so that mirror owners could control how much traffic it takes. Perhaps we should tweak weights so that only the fastest mirror is used unless it is unavailable. If you put modified tdm_installer anywhere, please mark it as tweaked by you in the window title. |
 |
The window isn't shown. I use the installer to automate asset downloading on package building, and I purposely created a tool that hides the window. https://gitlab.com/es20490446e/darkmod-linux https://gitlab.com/es20490446e/unwin The only thing that is modified is the mirror. At building time the mirror with the least amount of ping is selected. The installer isn't meant to be used after the package is built, and it isn't included inside the package. Anyway the builder is interpreted code, so anything it does is transparent. For instance it also completely deblobs all the sources and builds everything from source, for total transparency. https://gitlab.com/es20490446e/blobs The next improvement is compiling and building in parallel, so the package building takes likely the same time as without compiling. |
|
|
I mean downloading and compiling in parallel. |
|
|
I don't think I'll do anything about it in foreseeable future. The mirrors weighting system is designed to distribute load across mirrors, and it'd better remain like that. I have added a way to select one mirror in the GUI, users can use it if they want. By the way, I don't see much difference between mirrors from my location. |
- Anonymous
