Microsoft Introduced the new File System ReFS(Resilient File System) codenamed Protogon for its upcoming Windows 8 Server,which was built on the foundation of NTFS.
The new file system has been built keeping in mind the increasing demands of storage requirements for Windows,allowing a maximum handling of of 1 Yobibite of storage,shared storage pools across multiple machines ,as well as enhanced resiliency to corruptions.
Recently FirstEver posted the comparison between the benchmark results of ReFS v/s NTFS file systems,with the following test system:
CPU: Intel Corel 2 Duo E8400 @ 4.1GHz
Memory: 4GB Dual DDR2 PC2-9600 1200MHz
HDD 1: Samsung HD753LJ 750GB
HDD 2: Western Digital WD2500BEVS-60U?ST0 250GB
Operating System: Windows 8 Release Preview (build 8400) 64-bit
Here are some of the Test Results,
Copying a file of 3GB from one hard disk drive to another(NTFS to NTFS) took 83.74 seconds while for NTFS to ReFS it took 85.04 seconds.While copying a 4.10 GB file within a same hard disk had the following outcome,
Here are the results of the HD Tune 3.50 Benchmarks for both NTFS and ReFS file systems.
Results Of the FutureMark PCMark 7 Tests
If we compare the copying time in NTFS and in the new ReFS there is a notable difference between the copying times between those two,in the futuremark Tests however the ReFS stands better than NTFS in almost all the departments like gaming,starting applications and other heavy multimedia related work.
Checkout more benchmark Results Here
Building Windows 8 blog is back again with a new informative post,this time detailing the new upcoming File System named ReFS(Resilient File System) which is built on the foundation of highly popular NTFS file system.
The ReFS has been built keeping in mind the new improvements and innovations in the new generation of Storage devices and technologies and as with the earlier file system introductions,this one will also be first introduced for the Windows Server 8 only.
Here are the key Goals of ReFS :
- Maintain a high degree of compatibility with a subset of NTFS features that are widely adopted while deprecating others that provide limited value at the cost of system complexity and footprint.
- Verify and auto-correct data. Data can get corrupted due to a number of reasons and therefore must be verified and, when possible, corrected automatically. Metadata must not be written in place to avoid the possibility of “torn writes,” which we will talk about in more detail below.
- Optimize for extreme scale. Use scalable structures for everything. Don’t assume that disk-checking algorithms, in particular, can scale to the size of the entire file system.
- Never take the file system offline. Assume that in the event of corruptions, it is advantageous to isolate the fault while allowing access to the rest of the volume. This is done while salvaging the maximum amount of data possible, all done live.
- Provide a full end-to-end resiliency architecture when used in conjunction with the Storage Spaces feature, which was co-designed and built in conjunction with ReFS.
Features of ReFS are as follows:
- Metadata integrity with checksums
- Integrity streams providing optional user data integrity
- Allocate on write transactional model for robust disk updates (also known as copy on write)
- Large volume, file and directory sizes
- Storage pooling and virtualization makes file system creation and management easy
- Data striping for performance (bandwidth can be managed) and redundancy for fault tolerance
- Disk scrubbing for protection against latent disk errors
- Resiliency to corruptions with “salvage” for maximum volume availability in all cases
- Shared storage pools across machines for additional failure tolerance and load balancing
Checkout the detailed Post by Surendra Verma on ReFS here.