Differences

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

--- performance_tuning [2023/11/07 16:00] – johnsanc
+++ performance_tuning [2025/03/31 19:47] (current) – johnsanc
@@ Line 9: / Line 9: @@
 \\
 ==== Configure a cache ToSort on a fast drive ====
-RomVault processes fixes involving 7z archives by extracting the contents to a cache directory first then performing all fixes involving that archive in a batch. This behavior minimizes the number of times a solid 7z archive needs to be decompressed or recompressed. If no Cache ToSort is configured, then RomVault will use the Primary ToSort. If your Primary ToSort is on a slower drive or network share, you may experience sub-optimal performance with 7z archives. For more information about the Cache ToSort, refer to the section on [[tosort_directories|ToSort Directories]].
+RomVault processes fixes involving 7z archives by extracting the contents to a cache directory first then performing all fixes involving that archive in a batch. This behavior minimizes the number of times a solid 7z archive needs to be decompressed or recompressed. If no Cache ToSort is configured, then RomVault will use the Primary ToSort. If your Primary ToSort is on a slower drive or network share, you may experience sub-optimal performance with 7z archives. To prevent wear and tear on an NVME or SSD drive, you can also use a RAM Drive as a cache ToSort. For more information about the Cache ToSort, refer to the section on [[tosort_directories|ToSort Directories]].
+\\
+==== Disable "Double Check Delete" in RomVault's Global Settings ====
+The double check delete option is a safeguard that prevent's RomVault from deleting your only copy of a file in the case when your directory mappings are misconfigured. If you are confident in your setup and have never seen the double check delete error, then you can disable this option and delete actions will be much faster.
 \\
@@ Line 20: / Line 26: @@
 \\
-==== If using UnRAID, keep ToSorts on the same drive letter or share as the RomRoot ====
+==== Keep ToSorts on the same volume as the RomRoot ====
-RomVault can move complete TorrentZipped archives and uncompressed files quickly with a move operation instead of copy & delete. However, in order to perform this operation the source and destination must be on the same volume. For example, if you have an UnRAID array with a Downloads share and a Games share, you may want to create a rootshare so you can access both under the same drive letter or base UNC path. If you are moving files across shares or drive letters, a copy & delete operation will be used instead of rename.
+RomVault can move archives and uncompressed files quickly with a move operation instead of copy & delete. However, in order to perform this operation the source and destination must be on the same volume. For example, if you have an UnRAID array with a Downloads share and a Games share, you may want to create a rootshare so you can access both under the same drive letter or base UNC path. If you are moving files across shares or drive letters, a copy & delete operation will be used instead of rename.
-<WRAP info>The rename operation will not be used if the file to be moved resides on the cache pool and must be moved across shares, E.g. from Downloads to Games. To get around this and still use a cache pool, you should consider using a Downloads directory under your Games share so both the source and destination reside on the same share.</WRAP>
+<WRAP info>UnRAID Note: The rename operation will not be used if the file to be moved resides on the cache pool and must be moved across shares, E.g. from Downloads to Games. To get around this and still use a cache pool, you should consider using a Downloads directory under your Games share so both the source and destination reside on the same share.</WRAP>
 \\
 ==== Enable case sensitive SMB shares ====
-If you are using a SMB share, you should always configure this share to enable case sensitivity. If a SMB share is not explicitly configured for case sensitivity then you will have poor performance when working with very large directories because Samba must do a filename search and match on passed names. For more information please refer to the Name Mangling section of the [[https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html|Samba documentation]].
+If you are using a SMB share and have performance issue with RomVault fixing files in large directories, you can try enabling case sensitivity. If a SMB share is case insensitive then Samba will do a filename search and match on passed names. For more information please refer to the Name Mangling section of the [[https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html|Samba documentation]].
-<WRAP important>It is ALWAYS recommended to use case sensitive SMB shares with RomVault. Case insensitive SMB shares may result in an error while fixing due to changing character case of a filename.</WRAP>
+<WRAP important>It is recommended to use case sensitive SMB shares with RomVault in your underlying filesystem is also case sensitive. Case insensitive SMB shares may result in an error while fixing due to changing character case of a filename.</WRAP>
 <WRAP info>If you are an UnRAID user, this setting can easily be changed to "Yes" in the SMB Security Settings tab of your user share.</WRAP>
@@ Line 40: / Line 46: @@
 store dos attributes = no
 </code>
-These settings will prevent Samba from writing and reading extended attributes used for legacy DOS permissions.
+These settings will prevent Samba from writing and reading extended attributes used for legacy DOS permissions. Directory listing tests showed a 28% speed improvement.
 \\