On Sat, 2007-11-24 at 10:31 -0500, 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 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.
I think there's a compromise available here. "It's not THAT long of a wait" depends on the amount of repositories you have enabled, and how big those repositories are. For example, when I enable Packman repository, updater check runs significantly longer. I think the way to compromise here is to add an additional option. Mark certain repositories as being "checkable for updates." If I'm using updater, then only repositories that are enabled and marked as updateable would be checked. Otherwise, if it is only marked enabled, then you only get the full gamut when you go into software management.
-- ---Bryen--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org