Live data from Hacker News

7-Zip for Windows can now use more than 64 CPU threads for compression

7-zip.org

101–110 of 220 posts

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#101
post #13

Earlier quoted context omitted.

Not that many people care about zstd; I would assume most 7-zip users care about the convenience of the gui.

I use the right click context menu to run 7zip, why would you open a GUI?

That is a GUI!

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#102

Earlier quoted context omitted.

> other systems had been exceeding 64 cores since the late 90s. Windows didn’t run on these other systems, why would Microsoft care about them? > x86 arguably didn't ship >64 hardware thread systems until then because NT didn't support it For publicly accessible web servers, Linux overtook Windows around 2005. Then in 2006 Amazon launched EC2, and the industry started that massive transition to the clouds. Linux is b…

Windows NT was originally intended to be multi-platform.

NT was and continues to be multi-platform.

That doesn't mean every platform was or would have been profitable. x86 became 'good enough' to run your mail or web server, it doomed other architectures (and commonly OSes) as the cost of x86 was vastly lower than the Alphas, PowerPCs, and so on.

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#104
post #10

I worry that 7-Zip is going to lose relevance because lack of zstd support. zlib's performance is intolerable for large files and zlib-ng's SIMD implementation only helps here a bit. Which is a shame, because 7-Zip is a pretty amazing container format, especially with its encryption and file splitting capabilities.

There are lots of 7zip alike with zstd support (it's a plugin effectively). On [corporate] Windows NanaZip would be my choice as it's available in Windows store.

on anything else - either directly zstd or tar

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#105
post #29

Earlier quoted context omitted.

I use ZSTD a ton in my programming work where efficiency matters. But for sharing files with other people, ZIP is still king. Even 7z or RAR is niche. Everyone can open a ZIP file, and they don't really care if the file is a few MBs bigger.

What are you compressing with zstd? I had to do this recently and the "xz" utility still blows it away in terms of compression ratio. In terms of memory and CPU usage, zstd wins by a large margin. But in my case I only really cared about compression ratio

do you have examples where xz 'blows it away', not just zstd -3?

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#106
post #29

Earlier quoted context omitted.

I use ZSTD a ton in my programming work where efficiency matters. But for sharing files with other people, ZIP is still king. Even 7z or RAR is niche. Everyone can open a ZIP file, and they don't really care if the file is a few MBs bigger.

What are you compressing with zstd? I had to do this recently and the "xz" utility still blows it away in terms of compression ratio. In terms of memory and CPU usage, zstd wins by a large margin. But in my case I only really cared about compression ratio

in my experience using zstd --long --ultra -22 gives marginally better compression ratio than xz -9 while being significantly faster

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#107
post #37

Earlier quoted context omitted.

> Everyone can open a ZIP file, and they don't really care if the file is a few MBs bigger. You can use ZSTD with ZIP files too! It's compression method 93 (see https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT which is the official ZIP file specification). Which reveals that "everyone can open a ZIP file" is a lie. Sure, everyone can open a ZIP file, as long as that file uses only a limited subset of the Z…

> You can use ZSTD with ZIP files too! Support for which was added in 2020: > On 15 June 2020, Zstandard was implemented in version 6.3.8 of the zip file format with codec number 93, deprecating the previous codec number of 20 as it was implemented in version 6.3.7, released on 1 June.[36][37] * https://en.wikipedia.org/wiki/Zstd#Usage So I'm not sure how widely deployed it would be.

Most linux distributions have zip support with zstd.

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#108
post #76

Earlier quoted context omitted.

Most people won't use that GUI, but will right click file or folder -> 7-Zip -> Add To ... and it will spit out a file without questions. Granted Windows 11 has started doing the same for its zip and 7zip compressors. Same trick goes for opening archives or executables (Installers) as archives.

Let's chat about Windows 11 right-click menu. I'm pretty sure they hid all the application menu extensions to avoid worst-case performance issues.

Exactly it. 3rd parties injecting their extensions harmed performance, which people turn around and blame Microsoft for.

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#109
post #29

Earlier quoted context omitted.

I use ZSTD a ton in my programming work where efficiency matters. But for sharing files with other people, ZIP is still king. Even 7z or RAR is niche. Everyone can open a ZIP file, and they don't really care if the file is a few MBs bigger.

I don't know about, had a dicey situation recently where powershell's compress-archive couldn't handle archives >4GB and had to use 7zip. it is more reliable and you can ship 7za.exe or create self-extracting archives (wish those were more of a thing outside of the windows world).

[deleted]

Re: 7-Zip for Windows can now use more than 64 CPU threads for compression

#110
post #59

Earlier quoted context omitted.

> Copyright (c) 1989 - 2014, 2018, 2019, 2020, 2022 Mostly it seems nutty that, after all these years, they’re still updating the zip spec instead of moving on to a newer format.

The English language is awful, and we keep updating it instead of moving to a newer language. Some things are used for interoperability, and switching to a newer incompatible thing loses all of its value.

[deleted]
Post reply on HN