Quantum 6-01376-05 manual StorNext File System Tuning Windows Memory Requirements

Page 27

StorNext File System Tuning

Windows Memory Requirements

water mark is reached, for example 128. The Max water mark is for situations where memory is very tight. The normal purge algorithms takes access time into account when determining a candidate to evict from the cache; in tight memory situations (when there are more than 'max' entries in the cache), these constraints are relaxed so that memory can be released. A value of 1024 in a tight memory situation should work.

StorNext File System Tuning Guide

24

Image 27
Contents 01376-05 Copyright Statement Contents Underlying Storage System StorNext File System TuningRAID Cache Configuration RAID Write-Back Caching RAID Read-Ahead Caching RAID Level, Segment Size, and Stripe Size File Size Mix and Application I/O Characteristics Direct Memory Access DMA I/O TransferBuffer Cache NFS / Cifs Metadata Controller System Metadata NetworkStripe Groups FSM Configuration File SettingsAffinities ExampleBufferCacheSize StripeBreadthFsBlockSize InodeCacheSizeThreadPoolSize ForcestripeAlignmentSnfs Tools JournalSizeStorNext File System Tuning Metadata Controller System StorNext File System Tuning Metadata Controller System StorNext File System Tuning Metadata Controller System MountCommandOptions StorNext File System Tuning Metadata Controller System Hardware Configuration Distributed LAN Disk Proxy NetworksSnfs External API StorNext File System Tuning Guide Network Configuration and Topology SAN Windows Memory Requirements Distributed LAN ServersStorNext File System Tuning Windows Memory Requirements StorNext File System Tuning Windows Memory Requirements Sample FSM Configuration File MAXStripeBreadth StorNext File System Tuning Sample FSM Configuration File StorNext File System Tuning Sample FSM Configuration File StorNext File System Tuning Sample FSM Configuration File