Earlier quoted context omitted.
Well, only a lunatic would use ZIP with anything but DEFLATE/DEFLATE64
there are A LOT of zip files using lzma in the wild. also, how about people learn to use updated software? should newer video compression technologies not be allowed in mkv/mp4. if you cant open it, well.. then stop using 90ies winzip
7-Zip for Windows can now use more than 64 CPU threads for compression
91–100 of 220 posts
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#92Earlier quoted context omitted.
Wow. That's surprisingly lame.
The NT kernel dates back to 1993. Computers didn’t exceed 64 logical processors per system until around 2014. And doing it back then required a ridiculously expensive server with 8 Intel CPUs. The technical decision Microsoft made initially worked well for over two decades. I don’t think it was lame; I believe it was a solid choice back then.
(Now, NT for Sparc never actually became a thing, but it was certainly on Microsoft's radar at one point)
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#93Earlier quoted context omitted.
I mean, x86 didn't, but other systems had been exceeding 64 cores since the late 90s. And x86 arguably didn't ship >64 hardware thread systems until then because NT didn't support it.
> 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…
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#94Earlier quoted context omitted.
> new Office files I know what you mean, I’m not being pedantic, but I just realized it’s been 19 years. I wonder when we’ll start calling them “Office files”.
> I wonder when we’ll start calling them “Office files”. Probably around the same time the save icon becomes something other than a 3 1/2" floppy disk.
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#95Earlier quoted context omitted.
> new Office files I know what you mean, I’m not being pedantic, but I just realized it’s been 19 years. I wonder when we’ll start calling them “Office files”.
> I wonder when we’ll start calling them “Office files”. Probably around the same time the save icon becomes something other than a 3 1/2" floppy disk.
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#96I 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.
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#97Earlier quoted context omitted.
there are A LOT of zip files using lzma in the wild. also, how about people learn to use updated software? should newer video compression technologies not be allowed in mkv/mp4. if you cant open it, well.. then stop using 90ies winzip
>how about people learn to use updated software? How about software developers learn to keep software working on old OSes and old hardware?
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#98Earlier quoted context omitted.
there are A LOT of zip files using lzma in the wild. also, how about people learn to use updated software? should newer video compression technologies not be allowed in mkv/mp4. if you cant open it, well.. then stop using 90ies winzip
mkv or mp4 with h264 and aac is good enough. mp3 is good enough. jpeg is good enough. zip with deflate is also good enough.
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#99Why was there a limitation on Windows? I can't find any such limit for Linux.
Re: 7-Zip for Windows can now use more than 64 CPU threads for compression
#100Earlier quoted context omitted.
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
people tend to care about decompression speed - xz can be quite slow decompressing super compressed files whereas zstd decompression speed is largely independent of that. People also tend to care about how much time they spend on compression for each incremental % of compression performance and zstd tends to be a Pareto frontier for that (at least for open source algorithms)
Unfortunately for the hoster, they either have to eat the cost of the added bandwidth from a larger file or have people complain about slow decompression.