YagottaBKiddin

Indeed I do use Scanner + DrivePool (I mentioned this at the very bottom of the first post
 
It's not a shameless plug when it is good advice and a great deal!
 
I'll be converting my other 2012-R2 StorageSpace server over to DrivePool soon (already have the DrivePool key) and will be adding Scanner to it as well.  The integration of the two has come a long way in the past few years! (I've been a StableBit customer for a few years now).  

Good evening everyone.  I found this very interesting, fascinating even:
 
I had just set up a Windows 2012-R2 Storage Server, with ~20 TiB of drives to function primarily as a media server running Emby and file-server endpoint for various backups of machine images etc.  
 
CPU: Intel Core i7-4790K
RAM: 32 GiB DDR3 2666MHz.  
OS is hosted on an M.2 PCIe 3.0 x4 SSD (128 GiB) *screaming fast*. 
5 x 4 TiB HGST DeathStar NAS (0S003664) 7200 RPM/64 MB cache SATA-III
 
Initially, the machine was set up with one large mirrored storage pool (no hot spares) composed from 5 primordial 4 TiB HGST sata-III disks all connected to sata-III ports on the motherboard (Z97 based).
 
The graph below was taken during the process of copying ~199 files in multiple directories of various sizes (15K - 780 GiB) for a total of ~225 GiB.
 
 

Fig 1: Copy To Storage Spaces 2012-R2 mirrored pool
 
What isn't apparent from the graph above are the *numerous* stalls where the transfer rate would dwindle down to 0 for 2-5 seconds at a time. The peaks are ~50 MB/s. Took *forever* to copy that batch over.
 
Compare the above graph with the one below, which is another screenshot of the *exact* same batch of files from the exact same client machine as the above, at almost exactly the same point in the process. The client machine was similarly tasked under both conditions. The target was the exact same server as described above, only I had destroyed the Storage Spaces pool and the associated virtual disk and created a new pool, created from the exact same drives as above, using StableBit DrivePool (2.1.1.561), transferring across the exact same NIC, switches and cabling as above also. More succinctly: Everything from the hardware, OS, network infrastructure, originating client (Windows 10 x64) is exactly the same.
 
The only difference is that the pooled drives are managed by DrivePool instead of Storage Spaces:
 

Fig 2: Massive file transfer to DrivePool (2.1.1.561) managed pool.
 
What a huge difference in performance!  I didn't believe it the first time.  So, of course, I repeated it, with the same results.
 
Has anyone else noticed this enormous performance delta between Storage Spaces and DrivePool?
 
I think the problem is with the writes to the mirrored storage pool, I had no problems with stalls or inconsistent transfer rates when reading large batches of files from the pool managed by Storage Spaces. The write performance is utterly horrid and unacceptable!
 
Bottom Line: The combination of drastically improved performance with DrivePool over Storage Spaces, plus the *greatly* enhanced optics into the health of the drives provided with Scanner:  DrivePool + Scanner >>>> Storage Spaces.  Hands Down, no contest for my purposes. The fact that you can mount a DrivePool managed drive on *any* host that can read NTFS is another major bonus.  You cannot do the same with StorageSpace managed drives, unless you move all of them en-bloc.
 
Kudos to you guys!  <tips hat>
 

Good evening everyone.  I found this very interesting, fascinating even:
 
I had just set up a Windows 2012-R2 Storage Server, with ~20 TiB of drives to function primarily as a media server running Emby and file-server endpoint for various backups of machine images etc.  
 
CPU: Intel Core i7-4790K
RAM: 32 GiB DDR3 2666MHz.  
OS is hosted on an M.2 PCIe 3.0 x4 SSD (128 GiB) *screaming fast*. 
5 x 4 TiB HGST DeathStar NAS (0S003664) 7200 RPM/64 MB cache SATA-III
 
Initially, the machine was set up with one large mirrored storage pool (no hot spares) composed from 5 primordial 4 TiB HGST sata-III disks all connected to sata-III ports on the motherboard (Z97 based).
 
The graph below was taken during the process of copying ~199 files in multiple directories of various sizes (15K - 780 GiB) for a total of ~225 GiB.
 
 

Fig 1: Copy To Storage Spaces 2012-R2 mirrored pool
 
What isn't apparent from the graph above are the *numerous* stalls where the transfer rate would dwindle down to 0 for 2-5 seconds at a time. The peaks are ~50 MB/s. Took *forever* to copy that batch over.
 
Compare the above graph with the one below, which is another screenshot of the *exact* same batch of files from the exact same client machine as the above, at almost exactly the same point in the process. The client machine was similarly tasked under both conditions. The target was the exact same server as described above, only I had destroyed the Storage Spaces pool and the associated virtual disk and created a new pool, created from the exact same drives as above, using StableBit DrivePool (2.1.1.561), transferring across the exact same NIC, switches and cabling as above also. More succinctly: Everything from the hardware, OS, network infrastructure, originating client (Windows 10 x64) is exactly the same.
 
The only difference is that the pooled drives are managed by DrivePool instead of Storage Spaces:
 

Fig 2: Massive file transfer to DrivePool (2.1.1.561) managed pool.
 
What a huge difference in performance!  I didn't believe it the first time.  So, of course, I repeated it, with the same results.
 
Has anyone else noticed this enormous performance delta between Storage Spaces and DrivePool?
 
I think the problem is with the writes to the mirrored storage pool, I had no problems with stalls or inconsistent transfer rates when reading large batches of files from the pool managed by Storage Spaces. The write performance is utterly horrid and unacceptable!
 
Bottom Line: The combination of drastically improved performance with DrivePool over Storage Spaces, plus the *greatly* enhanced optics into the health of the drives provided with Scanner:  DrivePool + Scanner >>>> Storage Spaces.  Hands Down, no contest for my purposes. The fact that you can mount a DrivePool managed drive on *any* host that can read NTFS is another major bonus.  You cannot do the same with StorageSpace managed drives, unless you move all of them en-bloc.
 
Kudos to you guys!  <tips hat>