10:12 a.m.
Currently this defaults to 3. I have seen people online suggesting that they
get better performance setting it to 6 (or higher).
As mirror admins in 2022, do you care? Do you have a preference for our
default? Note that I'm 87% sure that GNOME Software does not do parallel
downloads so this would primarily affect server/cloud use cases (the later
of which should hit cloud-provider mirrors) and enthusiast usage.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
10:34 a.m.
On Wed, Jun 29, 2022 at 11:12 AM Matthew Miller <mattdm(a)fedoraproject.org>
wrote:
Currently this defaults to 3. I have seen people online suggesting
that
they
get better performance setting it to 6 (or higher).
As mirror admins in 2022, do you care? Do you have a preference for our
default? Note that I'm 87% sure that GNOME Software does not do parallel
downloads so this would primarily affect server/cloud use cases (the later
of which should hit cloud-provider mirrors) and enthusiast usage.
I'm pretty sure that the metalinks also include max parallel connections
per mirror information, as we set when we configured our mirrors. Raising
the client side number of connections should just mean more mirrors get
used, right?
If that's the case, I don't see a problem with it.
--
*Neal Gompa*
Senior DevOps Engineer
Datto, Inc.
www.datto.com
10:52 a.m.
On Wed, Jun 29, 2022 at 11:34:32AM -0400, Neal Gompa wrote:
On Wed, Jun 29, 2022 at 11:12 AM Matthew Miller
<mattdm(a)fedoraproject.org>
wrote:
> Currently this defaults to 3. I have seen people online suggesting that
> they
> get better performance setting it to 6 (or higher).
>
> As mirror admins in 2022, do you care? Do you have a preference for our
> default? Note that I'm 87% sure that GNOME Software does not do parallel
> downloads so this would primarily affect server/cloud use cases (the later
> of which should hit cloud-provider mirrors) and enthusiast usage.
As a mirror admin, I do not care.
I'm pretty sure that the metalinks also include max parallel
connections
per mirror information, as we set when we configured our mirrors. Raising
MirrorManager offers a way to specify max parallel connections, but that
is not used in the metalink at all. The existing value in the metalink
is hard-coded to 1. So that does also not really help. At this point
there is no support from the MirrorManager side.
Adrian
7:21 a.m.
On Wed, Jun 29, 2022 at 11:53 AM Adrian Reber <adrian(a)lisas.de> wrote:
On Wed, Jun 29, 2022 at 11:34:32AM -0400, Neal Gompa wrote:
> On Wed, Jun 29, 2022 at 11:12 AM Matthew Miller <
mattdm(a)fedoraproject.org>
> wrote:
>
> > Currently this defaults to 3. I have seen people online suggesting that
> > they
> > get better performance setting it to 6 (or higher).
> >
> > As mirror admins in 2022, do you care? Do you have a preference for our
> > default? Note that I'm 87% sure that GNOME Software does not do
parallel
> > downloads so this would primarily affect server/cloud use cases (the
later
> > of which should hit cloud-provider mirrors) and enthusiast usage.
As a mirror admin, I do not care.
> I'm pretty sure that the metalinks also include max parallel connections
> per mirror information, as we set when we configured our mirrors. Raising
MirrorManager offers a way to specify max parallel connections, but that
is not used in the metalink at all. The existing value in the metalink
is hard-coded to 1. So that does also not really help. At this point
there is no support from the MirrorManager side.
That should be fixed then, because the setting in MirrorManager that we set
literally says it goes into the metalink to give clients the info on the
maximum number of parallel connections that should be used with this mirror.
--
*Neal Gompa*
Senior DevOps Engineer
Datto, Inc.
www.datto.com
1:02 p.m.
Il giorno mer, 29/06/2022 alle 11.12 -0400, Matthew Miller ha scritto:
Currently this defaults to 3. I have seen people online suggesting
that they
get better performance setting it to 6 (or higher).
As mirror admins in 2022, do you care? Do you have a preference for our
default? Note that I'm 87% sure that GNOME Software does not do parallel
downloads so this would primarily affect server/cloud use cases (the later
of which should hit cloud-provider mirrors) and enthusiast usage.
Hi Matthew, nice to meet you. :)
Performance wise, It would be interesting if dnf could spread the
load among different mirrors—as in: "n" concurrent downloads, spread
among "n" different mirrors—and perhaps, round-robin among the other
available mirrors too.
This would help slow mirrors, fast clients, faltering pathways, etc.
--
Davide Repetto
<ReD(a)idp.it>
4:15 p.m.
On 6/29/2022 8:12 AM, Matthew Miller wrote:
Currently this defaults to 3. I have seen people online suggesting
that they
get better performance setting it to 6 (or higher).
As mirror admins in 2022, do you care? Do you have a preference for our
default? Note that I'm 87% sure that GNOME Software does not do parallel
downloads so this would primarily affect server/cloud use cases (the later
of which should hit cloud-provider mirrors) and enthusiast usage.
I don't see a particular issue with kicking it up to 6, but I'd be
somewhat hesitant (personally) going much past that. 3 you probably are
just around the threshold of each stream fighting for resources. 6 you
are probably in the realm of saturating what a clients downloads can
realistically pull and the streams fighting each other for bandwidth.
As was already mentioned, after 3 streams it might be worth pulling from
other mirrors simultaneously vs. pointing it all at a single mirror and
comparing bandwidth (that's obviously a bit more complex on dnf side of
things though).
If this can be done on a per-site basis maybe leaving the 1gbps and
lower mirrors at 3, and kicking greater than 1gbps up into the 6 streams
realm?
- John 'Warthog9' Hawley
12:36 a.m.
Hello,
as an mirror admin I don't care too. There is only one reason, that on
high load mirror's TCP connections will be flooded, but currently there is
no high load on new Fedora releases.
But as an user I prefer 1 connection only. On slow wifi networks with 3
parallell connection my network is downloading updates only, but for other
apps it's blocked. Network limits are divided into 4 connections (3 for dnf
and 1 for user) and most of capacity (75%) is used for updates and only
25% remains for user. With 6 connection it will be even worse.
I prefer to do not harm users when updates are downloaded. Downlad them
on background and leave users to work.
SAL
On Wed, Jun 29, 2022 at 11:12:29AM -0400, Matthew Miller wrote:
> Currently this defaults to 3. I have seen people online suggesting that they
> get better performance setting it to 6 (or higher).
>
> As mirror admins in 2022, do you care? Do you have a preference for our
> default? Note that I'm 87% sure that GNOME Software does not do parallel
> downloads so this would primarily affect server/cloud use cases (the later
> of which should hit cloud-provider mirrors) and enthusiast usage.
>
>
>
> --
> Matthew Miller
> <mattdm(a)fedoraproject.org>
> Fedora Project Leader
> _______________________________________________
> Mirror-admin mailing list -- mirror-admin(a)lists.fedoraproject.org
> To unsubscribe send an email to mirror-admin-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/mirror-admin@lists.fedorapr...
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
659
days inactive
660
days old
mirror-admin@lists.fedoraproject.org
6 comments
6 participants
participants (6)
-
Adrian Reber -
Davide Repetto -
John 'Warthog9' Hawley -
Ján ONDREJ (SAL) -
Matthew Miller -
Neal Gompa