Aaron Kulkis wrote: > Philippe Landau wrote: >> Aaron Kulkis wrote: >>> How do you propose that YAST improve network communication speed? >> Downloading in parallel. > > So, have the repository's disk-drive head bouncing back and > forth between multiple files, rather than staying on one > track until it's done... no, that does NOT speed up > communication speed..it slows it down further (and even > with striping (RAID 1), the principle still applies). Downloading several files at the same time is not a challenge. If you want to go down to hardware level, much is done with the help of RAM :-)
> Downloading in parallel only speeds up communication when > the different files being downloaded are on completely > different PHYSICAL disk drives. That's not very well > likely for the update files on a repository. > >> Checking for changes could be done in seconds. > > It's possible that there could be some optimizations > there... but I doubt it... checking for updates involves > a large amount of data to download -- or else risk > that a foul-up on one check means that you never see > that package as having an update until the NEXT > update AFTER THAT comes around. > > I'll stick with the fool-proof way of getting all > the version/update info every time. It's not THAT > long of a wait. It is, as Clayton states too: Clayton wrote: > If you have the patience to actually start it up. It takes forever to > refresh the repositories each and every time I launch the software > install component. I give up on it long before it ever finishes.. > After about 10 minutes I kill it and launch Smart. Less than a minute > to refresh, and I am using the same repositories. Bob Ewart detailed how checking for changes could be done in seconds, like in other distributions: > I agree with all the comments on fixing the software updater. That > really needs work. The other day, download.opensuse.org was timing out > for most of the morning(EST). According to a comment on the > repositories page, this is supposed to be a re-director to a local > repository. It should never be down. Maybe the initial interchange > with a repository should be a simple date stamp of the latest change. > That way downloading large lists could be avoided. I got a kick out of > the installation script for the MS fonts. It checks a number of sites > and picks the fastest one to respond. Kind regards Philippe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
