Differences

This shows you the differences between two versions of the page.

--- faq [2024/04/11 01:20] – johnsanc
+++ faq [2025/04/26 21:53] (current) – [How can I have RomVault ignore an entire directory?] johnsanc
@@ Line 27: / Line 27: @@
 ==== How can I have RomVault ignore an entire directory? ====
-Only directories with a DAT will display in the tree. If your preferred organization setup requires ignoring a directory in your RomRoot, then you can use a placeholder DAT to make that directory appear in the tree which you can deselect or lock. The placeholder DAT only needs to contain this: <?xml version=“1.0”?><datafile/>
+Only directories with a DAT will display in the tree. If your preferred organization setup requires ignoring a directory in your RomRoot, then you can use a placeholder DAT to make that directory appear in the tree which you can deselect or lock. The placeholder DAT only needs to contain this: ''<?xml version="1.0"?><datafile/>''
-==== Why is LZMA so slow? ====
+==== What archive type should I use? ====
-Although LZMA has an excellent compression ratio, it is unfortunately single-threaded. RomVault uses maximum compression for LZMA, similar to torrent7zip. Compression and decompression are simply slow. LZMA may not be the best choice unless your goal is maximum space savings for archival purposes.
+Refer to the wiki page about [[archive_types|Archive Types]].
-==== Why is ZSTD compression so slow? ====
-RomVault's implementation of ZSTD uses compression level 19 without any additional parameters or long distance matching. ZSTD is multi-threaded but each thread or worker is assigned a job of a specific size. ZSTD level 19 uses a job size of 32 MiB. This means any compression stream under 32 MiB will only using a single worker. Conversely a stream of 500 MiB will use up to 16 workers simultaneously.