|
Scanning |
  
|
|
Scanning |
|
Scanning options provide a level of control over file system analysis operations.
Reparse Points
| • | Follow reparse points - Reparse points are available only within certain Windows operating systems, such NT/2k/XP. They allow for specific types of actions (such as redirection) to occur during the parsing of file system paths. Mount points and symbolic links (also known as directory junctions) are forms of reparse points. Generally speaking, you will not want FolderSizes to follow reparse points – doing so can cause the inclusion of duplicate or unintuitive paths. |
Performance
| • | Cache file owner lookup data across multiple scans - When enabled, this option stores (or caches) file owner data for files that it encounters, speeding up file owner lookup operations for future scans. You should strongly consider enabling this option when scanning remote (network) file systems. Note that cache values are held in memory until FolderSizes is terminated or the cache is manually cleared (see below). |
| o | For remote (network) paths only - By default, file owner data will be cached for remote file system paths only. Remote paths are those accessible through mapped drives and/or UNC path (e.g. "\\server\share") notation. |
| o | Maximum cache memory allocation - Designates the maximum amount of memory (in Kb) that can be consumed by the file owner data lookup cache. If you're scanning large remote file systems and have a lot of memory in the FolderSizes host computer, consider doubling or tripling the default value of 2048. |
| o | Clear cache now - Click this button to purge the file owner data lookup cache immediately. |
File System Redirection
| • | Disable WOW64 file system redirection when running on 64-bit computers - This option, enabled by default, disables file system redirection on computers running a 32-bit version of FolderSizes on a 64-bit Windows operating system. Applies to Windows Vista and later only. |
Early Data Binding
Normally, FolderSizes will extract file system object ownership data as late as possible (during report display, typically) to improve overall file system analysis performance.
Sometimes, however, it may be preferable to extract file ownership data as early as possible (during file system scanning). For example - in the case where remote file systems are being analyzed over slower network connections, performance of operations such as report display and XML export may be improved with early data binding enabled.