Search: Advanced search
Browse by category:
Performance tuning for concurrent file access through NFS-mounted Bloombase StoreSafe virtual storage
Multi-threaded applications having file access on Spitfire StoreSafe NFS virtual storages experience slow response during file read and write.
Highly multi-threaded applications with intense file read/write access experiences slow response and file I/O may not reach the maximum available performance through NFS-mounted Spitfire StoreSafe virtual storage under the following environment :
By default, Spitfire StoreSafe file I/O operations via NFS mount point is synchronized made possible by system environment variable
Under certain circumstances where huge volume of file I/O is in place, multi-threading file write operations may serialized and have performance drop if read/write operations are sychronized.
By default, file I/O synchronization
As a performance tuning alternative, this parameter should be removed.
By doing this, multi-threading file I/O via NFS-mounted Spitfire StoreSafe virtual storage is not synchronized. The performance may have at least 20% increase. This can be done by removing
parameter in Spitfire StoreSafe system startup file.
For applications where concurrent file I/O volume is not huge or application itself has extensive caching capabilities, this application note is not applicable. Examples of these include
Enterprise applications without tight file read/write serialization control should avoid using this performance tuning or it may introduce data integrity issues. Customers are recommended to trade performance for data integrity. Examples include
The parameter may be obsoleted in the future release of Spitfire StoreSafe, however, it can be enabled manually upon request.