Having every single pkg client open this many connections in parallel by
default scares me.
Running multiple transient connections in parallel winds up bypassing
many of TCP's congestion controls; each new tcp connection needs to
"re-learn" the path capacity. If 20 parallel connections turns out to
be too many in practice, how will we be able to throttle clients back?
In particular, I'd strongly suggest adding a mechanism to the client --
such as a parameter published by a repo which is fetched and obeyed by
the client -- so that if 20 or whatever number we pick turns out to be
bad we can tune it downward *at a repo that's melting* rather than
waiting for clients to be updated to a newer version of the pkg tools.
- Bill
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
