Differences

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

--- performance_tuning [2022/01/02 17:41] – johnsanc
+++ performance_tuning [2024/01/06 18:14] (current) – johnsanc
@@ Line 20: / Line 20: @@
 \\
-==== Enable case-sensitive SMB shares ====
+==== If using UnRAID, keep ToSorts on the same drive letter or share as the RomRoot ====
-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]].
+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.
-|**💡 TIP:** \\ 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 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>
+\\
+==== Enable case sensitive SMB shares ====
+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 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>
+\\
+==== Disable extended attributes with SMB settings ====
+Some Samba settings can greatly improve performance, especially for directory listing and traversal. Consider adding these SMB settings to your NAS configuration:
+<code>
+ea support = no
+store dos attributes = no
+</code>
+These settings will prevent Samba from writing and reading extended attributes used for legacy DOS permissions. Directory listing tests showed a 28% speed improvement.
 \\
@@ Line 37: / Line 54: @@
 One of the most common causes of poor performance is other disk activity. If you are having poor performance with scanning or fixing operations, try closing other programs that may be adding to disk load, for example torrents or indexing/hashing services.
+\\
+==== Get more RAM ====
+RomVault uses a significant amount of RAM for its cache in order to perform much faster than a SQL database. Its recommended to have at least 1 GB of RAM per 1,000,000 ROMs managed by RomVault.
+\\
+==== Use multiple RomVault instances if RAM is limited ====
+RomVault loads information from all DATs into memory which can use a significant amount of RAM. If you do not have enough RAM for the amount of DATs you have, you can use more than one instance of RomVault. For example all TOSEC DATs could be loaded using one instance and all Redump DATs with another. If you take this approach be sure that each instance is running from a separate directory so the cache files are not shared.