Even on SSD, the CPU is many times faster than the fastest SSD drive.
Could this be why?
The .NET runtime team recently has incorporated zlib-ng into their codebase, and their System.IO.Compression ZipFile implementation is now using it -- which is where I got the 19 seconds from. https://github.com/dotnet/runtime/pull/102403
Consider using zlib-ng for deflate/inflate
I've also seen sporadic build errors with -j due to the target directory sometimes not getting created before the first ASMC output completes and tries and fails to write to the output location. Since I was batching my builds together into a shell script I just pre-created the directories beforehand in my script before calling make.
Is there an expected behavior for these two properties? It seems like every other handler in the project returns UInt64 for these two properties, except the LzhHandler, which returns UInt32.
I'm working, I just needed to add clang to my VS2022 components. I've actually written a build script that builds Format7zF for Windows x64 and Arm64, then drops into WSL and builds Linux x64/Arm64 as well as MacOS x64/Arm64. I changed the default build script to build .dylib for MacOS instead of .so files. Also, x64 MacOS didn't seem to use ASM=1, so I modified it for that and used https://github.com/gitGNU/objconv to convert the output from ASMC Linux x64 to Mach-O format so I could get MacOS x64...
Details with 24.05: Name: ffmpeg-N-115376-git-aff24c165-win32-nonfree-shared.tar Size: 7 733 248 Packed Size: 2 194 895 ------------------------: Size: 0 Packed Size: 0 Folders: 0 Files: 1 ------------------------: Path: \Downloads\ffmpeg-N-115376-git-aff24c165-win32-nonfree-shared.tar.zst Type: zstd Physical Size: 2 194 895 Streams: 1 Blocks: 60 Method: decoded: XXH64 wnd-desc-log-MAX:27 wnd-MAX:128MiB unknown-content-size ------------------------: ------------------------: Testing reveals: Data...