-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Chuck Anderson wrote:
On Sun, Oct 25, 2009 at 06:46:05PM -0400, Ben Boeckel wrote:
Seeing as it is a mirroring daemon, the network is the bottleneck. If it
isn't
then either you're sitting next door, our implementation is bad, or the hardware shouldn't be a mirror in the first place.
Speaking from experience, the network isn't always the bottleneck. I/O performance is often a performance problem, especially when walking the directory tree to build filelists.
AIUI, the tree will only be walked over during update composition and applying an update to the mirror (updates are done out-of-tree so that there is no catching a server "with its pants down" per se.
CPU performance can come into play if you are performing hashes or compression of the data to be transferred.
Yes, we'll have to keep an eye on this. As things come down from the tubes, the hashes should be working so they'll most likely be waiting on the network to get done with its files.
I suggest you post your message to the Fedora mirror-list-d where I'm sure you'll get lots of feedback.
Will do. Thanks for the tip.
- --Ben