3 ms·
In my experience, diff + diff + diff = super-long update process. It was done for many game updates up to several years ago, and an update from the box version
by Groxx 15y ago
In my experience, diff + diff + diff = super-long update process. It was done for many game updates up to several years ago, and an update from the box version through 3 patches could take up to an hour. The install, meanwhile, would take 20 minutes or so at most.
edit: not that I don't think this can be improved, nor that the updating software they used was any good. Just sayin'.
- GrandMasterBirt 15y agoThat directly depends on the install process for a small update. The diff minimizes traffic, the installer can just do a single install using 100 diffs. Each piece in the domino stack must play well together.
- idonthack 15y agoi expect those game updates didn't use bindiffs, they had to repackage the entirety of each updated file. when you consider that many developers do things like compress all game content files into a few large archives, it's easy to see how that adds up. you end up re-downloading the same content repeatedly when they repeatedly make small changes to a few scattered files in one large archive.
- dspillett 15y agoOften with game updates to get around the fact that patching the compressed multi-asset files directly would not be efficient (as a change early in the file would mean the rest of the file to the end would need patching unless they had the foresight to use something like gzip's rsync-friendly option), the patch would unpack the compressed resource files, patch them, then recompress. Depending on how granularly the assets are distributed amongst the installed files and how many of them were being touched by the patch this could be a lot slower than just reading the compressed file from CD to hard-drive which is what the installer would do. Of course this means that if using the multi-diff method of update distribution you would need to be careful about your selection of compression arrangement to avoid the same inefficiency (unless the saving in bandwidth for the client and the package storage servers is far more important than a bit of extra time spent on the updates client-side)..