From 2aaa0d96a0a5e6b5e9ca2fca30253d1893460444 Mon Sep 17 00:00:00 2001 From: Maxim Date: Mon, 25 Nov 2024 15:16:27 +0000 Subject: [PATCH] Readme update --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d997301..6d6784d 100644 --- a/README.md +++ b/README.md @@ -114,9 +114,9 @@ How to read: - Each colour group has a larger point showing the mean result across the corpus, with error bars showing one standard deviation. - There are lines showing the mean performance of zip and 7z on the same corpus. - There are two reference points to show the performance of loading uncompressed data, via the simplest and fastest methods. -- The "Pareto front" is shown by the dotted line. This connects all the compressors which can't be beaten on compression without being slower, or can't be beaten on speed without losing some compression. This is very much dependent on my test data and averaging method, your data may have a different frontier. It also ignores the size of the decompressor: the fast Phantasy Star Gaiden decompressor is over 1KB. So it's not a trivial solution. +- The "Pareto front" is shown by the dotted line. This connects all the compressors which can't be beaten on compression without being slower, or can't be beaten on speed without losing some compression. This is very much dependent on my test data and averaging method, your data may have a different frontier. The fast Phantasy Star Gaiden decompressor is ignored because its lookup tables mean the code is over 1KB - you may prefer that. -There can be wide variation in performance between compressors depending on your data; you may want to try a few options for your specific use case. +There's no trivial answer to the quesiton "which compressor is best". There can be wide variation in performance between compressors depending on your data; you may want to try a few options for your specific use case. Other compressors ----