Painfully slow downloads from OBS API leading to Connection broken error
Hi, For the last week or so, perhaps a bit longer, my attempts to branch and work on any OBS package has been hampered by the extremely slow download speeds of files via the API. For example, trying to `osc bco openblas`, I can barely download the patch and spec files (at around 10-20 KiB/s!!!) whereas the downloading of the source tarball itself proceeds at similar snail's pace for a bit and eventually ends with something like:
Connection broken: IncompleteRead(6935464 bytes read, 17469448 more expected)
thus making my working dir unusable. I thought this may have been some temporary network issue on my side, but apparently not: I can still `zypper dup` my TW system at ~10 MiB/s consistently, so eventually I came around to the idea that API based downloads when using osc are perhaps hitting a very slow mirror (I have been in India during this time, if that helps). Is there a way to avoid the auto-detection of mirrors for API downloads and specify a particular mirror to use instead? Or, any other workaround to resume branching and working on packages involving large-ish source tarballs — it seems downloading anything beyond a couple of MiB is impossible right now? Thanks in advance. -- Atri
On Sun, May 12 2024 at 08:36:37 AM +00:00:00, Atri Bhattacharya
Hi, For the last week or so, perhaps a bit longer, my attempts to branch and work on any OBS package has been hampered by the extremely slow download speeds of files via the API. For example, trying to `osc bco openblas`, I can barely download the patch and spec files (at around 10-20 KiB/s!!!) whereas the downloading of the source tarball itself proceeds at similar snail's pace for a bit and eventually ends with something like:
Connection broken: IncompleteRead(6935464 bytes read, 17469448 more expected)
thus making my working dir unusable. I thought this may have been some temporary network issue on my side, but apparently not: I can still `zypper dup` my TW system at ~10 MiB/s consistently, so eventually I came around to the idea that API based downloads when using osc are perhaps hitting a very slow mirror (I have been in India during this time, if that helps).
Is there a way to avoid the auto-detection of mirrors for API downloads and specify a particular mirror to use instead? Or, any other workaround to resume branching and working on packages involving large-ish source tarballs — it seems downloading anything beyond a couple of MiB is impossible right now?
Hi Atri, There is no mirrors involved in accessing the API, access to the API is done entirely through connecting to the OBS server in Prague. If you want to download a published package, your best bet is using the download repositories (accessible from download.opensuse.org), assuming you find any that include the OBS repositories in your area that are faster (there's a full list of mirrors that have it available [1]). Otherwise, you may want to figure out what changed about your network access that limits the connection speed between you and the OBS server to speed up your access to the API. [1] https://download.opensuse.org/report/mirrors?project=repositories Thanks, Jacob Michalskie
participants (2)
-
Atri Bhattacharya -
Jacob Michalskie