James Daniel

Thanks - I was wondering what the "Solid" setting meant, but hadn't got round to looking into it. Also for the explanation as to why incremental additions to an archive don't compress the way a single invocation does. I doubt I will get round to doing anything about this for the foreseeable future. The shape and size of this problem will change at a certain stage in this project, when the database becomes too active for zipping it to be a viable strategy. At that point we'll have to start using a...

Thanks - I was wondering what the "Solid" setting meant, but hadn't got round to looking into it. Also for the explanation as to why incremental additions to an archive don't compress the way a single invocation does. I doubt I will get round to doing anything about this for the foreseeable future. The shape and size of this problem will change at a certain stage in this project, when the database becomes too active for zipping it to be a viable strategy. At that point we'll have to start using a...

Thanks - I was wondering what the "Solid" setting meant, but hadn't got round to looking into it. Also for the explanation as to why incremental additions to an archive don't compress the way a single invocation does. I doubt I will get round to doing anything about this for the foreseeable future. The shape and size of this problem will change at a certain stage in this project, when the database becomes too active for zipping it to be a viable strategy. At that point we'll have to start using a...

Thanks - I was wondering what the "Solid" setting meant, but hadn't got round to looking into it. Also for the explanation as to why incrmental additions to an archive don't compress the way a single invocation does. I doubt I will get round to doing anything about this for the foreseeable future. The shape and size of this problem will change at a certain stage in this project, when the database becomes too active for zipping it to be a viable strategy. At that point we'll have to start using a...

Thanks guys. I have succeeded in making a 7z archive containing several identical binary files, the archive being not much more than the size of one of them. The settings I used were: Comp level: fastest Comp method: LZMA2 Dictionary Size: 1536Mb Word Size: 273 Solid Block Size: 32GB (but see my note following) Threads: 1 The solid block size apparently needs to be at least as big as the total size of the input material. So if there are 10 x 800MB files to compress, I found it needed a SB size of...

Thanks guys. I have succeeded in making a 7z archive consisting of several identical binary files, which is not much more than the size of one of them. The settings I used were: Comp level: fastest Comp method: LZMA2 Dictionary Size: 1536Mb Word Size: 273 Solid Block Size: 32GB (but see my note following) Threads: 1 The solid block size apparently needs to be at least as big as the total size of the input material. So if there are 10 x 800MB files to compress, I found it needed a SB size of at least...

Using 7zip 19.00 x64 on win10 64 bit. I am getting a stream (one per day) of binary files from a database platform. Each day's file may be identical (except for minor differences in file name, date etc.) to the previous one (I have checked with a file compare) or may have minor content differences. Files to date (over a period of four years) have been in the range 100Mb - 800Mb. I hope to be able to 7z two of these files into the same archive and get an archive size significantly less than the sum...

Using 7zip 19.00 x64 on win10 64 bit. I am getting a stream (one per day) of binary files from a database platform. Each day's file may be identical (except for minor differences in file name, date etc.) to the previous one (I have checked with a file compare) or may have minor content differences. Files to date (over a period of four years) have been in the range 100Mb - 800Mb. I hope to be able to 7z two of these files into the same archive and get an archive size significantly less than the sum...