From b9e8784d8d6806e733d0b4207731bf895d1c14db Mon Sep 17 00:00:00 2001 From: ckolivas Date: Fri, 13 Feb 2026 14:04:24 +1100 Subject: [PATCH] Update FAQ. --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 9bab3e0..b8c2189 100644 --- a/README.md +++ b/README.md @@ -403,6 +403,19 @@ almost 3 times slower. > A: For reasons that are unclear the later versions of libzpaq create corrupt archives when included with lrzip +> Q: When limiting processors with the -p option, lrzip still spawns twice as +many threads as specified with LZMA compression. + +> A: LZMA compression uses a separate set of threads of its own. Should the +number of threads be critical for your application, set it to half the amount +you wish it to use. + +> Q: Lrzip uses enormous amounts of resources. + +> A: That is by design to obtain the maximum amount of compression in the +minimum amount of time. It should not be used on a production server unless +coupled with options to limit both its processor and ram resources. + #### LIMITATIONS Due to mmap limitations the maximum size a window can be set to is currently 2GB on 32bit unless the -U option is specified. Files generated on 64 bit