View Single Post
  #39  
Old Today, 08:26
panker1992's Avatar
panker1992 panker1992 is offline
Registered User
 
Join Date: Oct 2015
Location: Always Somewhere
Posts: 605
Thanks: 127
Thanked 970 Times in 343 Posts
panker1992 is on a distinguished road
Let me give a definitive answer to this and actually show you what happens to the code.

bzip3, on this filter by default uses half your cores, and the blocksize is 16mb. when the block is integer 2047 mb, you need one more block for the compressed data, so
you need 4 gb RAM per thread to have that big block <2GB>.

what i did was to restrain the filter to have upper Limit to 256mb, because that is plenty, also there is one thing more, you can use deduplication before this.

i suggest that people avoid using hefty and beefy settings on CLS filters, especially when you can't predict a clear chain which will lead all the ram to be used on the main executable and therefore crash.

I generally not creating 32 Bit Applications anymore, however i decided to go friendly on people's RAM.

x86 for me is a compatibility area where my code simply has to decompress. and to be friendly for the 32 bit anything above 256mb as a block and multithreading decompression will kill it

i also fixed with hot patch redownload bzip3
Attached Images
File Type: png image.png (47.1 KB, 18 views)
__________________
My projects : Masked Compression, lzma2(xz) on Freearc, Zstd compressor for windows
My optimizations : packjpg.exe, zstd, lzham, precomp-dev-0.45.
Reply With Quote