Talk:Zstd

This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Software: Computing Low‑importance This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.SoftwareWikipedia:WikiProject SoftwareTemplate:WikiProject Softwaresoftware Low This article has been rated as Low-importance on the project's importance scale. This article is supported by WikiProject Computing. Computing: Software / Free and open-source software Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing Low This article has been rated as Low-importance on the project's importance scale. This article is supported by WikiProject Software (assessed as Mid-importance). This article is supported by Free and open-source software (assessed as Low-importance).

Initial stub created from existing French & Russian articles. —Hobart (talk) 00:31, 3 September 2016 (UTC)Reply

Just updated from ru:~ `a5b (talk) 05:51, 24 January 2018 (UTC)Reply

This article contains a translation of Zstandard from fr.wikipedia.

This article contains a translation of Zstandard from ru.wikipedia.

Should the comparison from Zstd to gzip better be replaced by Zstd vs. zlib as these are the algorithms, while gzip and zip are the interfaces to zlib or the container formats?--Massimo.b (talk) 07:35, 7 November 2017 (UTC)Reply

I agree with your sentiment. Furthermore, this starting sentence is technically incorrect: Zstandard was designed to give a compression ratio comparable to that of the DEFLATE algorithm. Because DEFLATE is not an algorithm but a compressed data format Abalib (talk) 03:29, 18 January 2020 (UTC)Reply

Zstandard reaches the Pareto frontier, which means it decompresses faster than any other currently-available algorithm with similar or better compression ratio.

While certainly Zstandard may be reaching the frontier, which is described in the second part of the sentence, how is that a Pareto frontier? The author has been pinged. -- wikimpan (Talk) 14:39, 4 January 2019 (UTC)Reply

The Pareto Frontier is a technical term for the set of combinations of parameters that are maximally Pareto efficient, meaning that any attempt to improve one thing (such as compression ratio) will make something else worse (such as speed, or memory use). The use of "frontier" is technically correct: it's currently maximally pareto efficient because we haven't found anything better, not because we've proven that nothing better exists. However the use of "which means" puts the inference backwards.

That said, the whole article needs a NPOV adjustment as parts of it border on hyperbole, and it needs a much better non-technical explanation.Martin Kealey (talk) 13:52, 19 April 2019 (UTC)Reply

see at ZIP (file format) - Wikipedia 2A02:6D40:34DC:7801:1867:F2BA:CE95:7BF4 (talk) 15:09, 27 July 2022 (UTC)Reply

zstd's effective lowest compression level right now is -131072, not -7 as this article currently claims. Could someone more versed in wikiwizardry make the edit and cite the man page?

(From said man page, the part about the targetLength parameter: "For ZSTD_fast, it triggers ultra-fast mode when > 0. The value represents the amount of data skipped between match sampling. Impact is reversed: a larger targetLength increases compression speed but decreases compression ratio."; "The minimum tlen is 0 and the maximum is 128 KiB." this limits the minimum level to -128 KiB, that is -131072)