Bug 410779 - Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink
Summary: Slow or unreliable downloads of KDE Neon release images and lack of adoption ...
Status: RESOLVED MOVED
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-10 05:23 UTC by Kristopher Ives
Modified: 2019-08-12 13:28 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher Ives 2019-08-10 05:23:19 UTC
SUMMARY
Sometimes downloading the latest KDE Neon release image (ISO) can be slow as well as unreliable. Download speeds can range in 200KB/s range and sometimes after waiting for 30 minutes the download simply fails, even when the client-side has a network connection that can easily handle 15MB/s.


STEPS TO REPRODUCE
1. Go to neon.kde.org
2. Download an ISO image

OBSERVED RESULT
Download is slow and sometimes fails. Since most users download via web browsers the failed downloads often cannot be resumed without additional workarounds.


EXPECTED RESULT
A 1.4GB download shouldn't take that long and shouldn't be a bottleneck to setting up KDE Neon for the first time.


ADDITIONAL INFORMATION
The current proposed solution on neon.kde.org is to use Metalink files as one is generated for every file that is mirrored. However, Metalink isn't well adopted so most users don't know how to use the files and the software availability for some platforms may be scarce.

The metalink files themselves do contain enough information in them to generate .torrent files that don't require any additional infrastructure. This means users can use their BitTorrent clients to download KDE Neon and the files will get pulled from the mirror servers via HTTP while also allowing any peers to seed to each other potentially reducing the bandwidth footprint on the mirrors.

I created a Python tool that converts .meta4 files into .torrent files with web seeds that shows how this can be done. An example of this is also hosted at https://metalink.xyz to show it works.

Please let me know what roadblocks exist in getting this functionality on neon.kde.org for downloads.
Comment 1 Kristopher Ives 2019-08-10 05:23:45 UTC
metalink-to-torrent source code https://github.com/krisives/metalink-to-torrent/blob/master/generate-torrent.py
Comment 2 Harald Sitter 2019-08-12 01:02:18 UTC
Stellar work! This looks like a really smart solution.

Before we can do anything you'll need to make your code free software though. We have a wiki page going into great detail on the matter [1], what you want to do is a pick a license an stick a license header into your source file.

https://community.kde.org/Policies/Licensing_Policy
Comment 3 Kristopher Ives 2019-08-12 05:27:43 UTC
Thanks for reminding me. I have released it under the MIT license. Please let me know if there is anything else I can do to help.
Comment 4 Harald Sitter 2019-08-12 10:28:23 UTC
Perfect, thanks. I've opened a task to implement this https://phabricator.kde.org/T11388