Filter
Top Products
StorNext File System Tuning
The Metadata Controller System
StorNext File System Tuning Guide 13
ThreadPoolSize 0
This setting consumes up to 512 KB memory times the number specified.
Increasing this value can improve concurrency of metadata operations.
For example, if many client processes are executing concurrently, the
thread pool can become exhausted by I/O wait time. Increasing the
thread pool size permits hot cache operations to be processed that would
otherwise be backed up behind the I/O-bound operations. There are
various O/S limits to the number of threads that can cause fatal problems
for the FSM daemon, so it's not a good idea to set this setting too high. A
range from 32 to 128 is recommended, depending on the amount of
available memory. It is recommended to size it according to the
max
threads
FSM hourly statistic reported in the cvlog file. Optimal settings
for
ThreadPoolSize range from 32K to 128K.
Example:
ThreadPoolSize 32 # default 16, 512 KB memory per thread
ForcestripeAlignment 0
This setting should always be set to Yes. This is critical if the largest
StripeBreadth defined is greater than 1MB. Note that this setting is not
adjustable after initial file system creation.
Example:
ForcestripeAlignment Yes
FsBlockSize 0
The FsBlockSize (FSB), metadata disk size, and JournalSize settings all
work together. For example, the FsBlockSize must be set correctly in
order for the metadata sizing to be correct. JournalSize is also dependent
on the FsBlockSize.
For FsBlockSize the optimal settings for both performance and space
utilization are in the range of 16K or 64K.Settings greater than 64K are not
recommended because performance will be adversely impacted due to
inefficient metadata I/O operations. Values less than 16K are not
recommended in most scenarios because startup and failover time may
be adversely impacted. Setting FsBlockSize to higher values is important
for multiterabyte file systems for optimal startup and failover time.