Skip to content

Make ZYPP_MULTICURL=0 the default #612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bmwiedemann opened this issue Feb 6, 2025 · 1 comment
Open

Make ZYPP_MULTICURL=0 the default #612

bmwiedemann opened this issue Feb 6, 2025 · 1 comment

Comments

@bmwiedemann
Copy link
Member

We found in past benchmarks that ZYPP_MULTICURL=1 logic is always slower than ZYPP_MULTICURL=0 downloads, because TCP connections need a while to reach their maximum speed and because latency is a major factor when downloading in small chunks.

We should make ZYPP_MULTICURL=0 the default.

For that, we need to ensure, we have good automatic fallbacks, so that users don't get to see 404 errors, connection timeouts and such when we can avoid it.

Fallback could go to download.o.o, cdn.o.o or downloadcontentcdn.o.o - probably an URL provided by MirrorCache.

CC @dirkmueller @andrii-suse

@bmwiedemann
Copy link
Member Author

I need to do some more measurements.
I found ZYPP_MULTICURL=0 made things worse on the two systems I tested on. One was a VM in Singapur(Hetzner) and another was a Nuremberg machine on a slow powerline connection.

The measurements showed significant improvements from a hot CDN cache there. It changed the time from 110s to 10s. When using https://downloadcontentcdn.opensuse.org/tumbleweed/repo/oss/ the difference was 368s to 3.6s but I we do not want to use that mode widely as the large files make it too slow and costly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant