Hey !
I've created an account especially to thank you Andrea for your work.
I've used Snapraid V1.0 on a Windows7 64bits (NAS+HTPC+torrent dl) for about a month and totally love it, so I'm pleased to see this new release 1.1 with a few new minor features and performance increase on the Windows side. Looks great !
I've just download it, reconfigured the conf, and started a new sync form scratch.
Configuration:
_ AMD Zacate APU E-350 1.6GHz (low power CPU!) on a Sapphire Pure Fusion Mini E350 motherboard.
_ 4Go DDR3
_ Windows 7 64-Bits on a Vertex SSD
_ 5 WD 2To Disk (WD20EARS) for Data
_ 1 WD 2To Disk (WD20EARS) for Parity
All disks are connected using SATA3 (even if not SATA3 ready of course), no USB or anything else.
My 2To disks are NTFS formated with 64K block-size and WesternDigital Advanced Format is activated. 95% of my data total volume is MKV files with an average size of about 7 Go. The other 5% are FLAC music (~20Mo), photos (~3Mo), and small text (but not many files).
Conf file:
Code:
# Example configuration for snapraid for Windows
# Defines the file to use as Parity storage
# It must NOT be in a data disk
# Format: "parity FILE_PATH"
parity P:\\parity
# Defines the file to use as Q-Parity storage
# If specified, it enables a double failures protection like RAID6
# It must NOT be in a data disk
# Format: "q-parity FILE_PATH"
#q-parity F:\\qar\\q-parity
# Defines the file to use as content list
# You can use multiple specification to store more copies of the file
# It's suggested to have at least N+1 copies of the file, where N is the number of parity files.
# It must NOT be in a data disk
# It can be in the disks used for parity storage
# Format: "content FILE_PATH"
content P:\\content
content C:\\SnapRaid\\content
# Defines the data disks to use
# The order is relevant for parity, do not change it
# Format: "disk DISK_NAME DISK_MOUNT_POINT"
disk d1 W:\\
disk d2 X:\\
disk d3 V:\\
disk d4 U:\\
disk d5 T:\\
# Defines files and directories to exclude
# Remember that all the paths are relative at the mount points
# Format: "exclude FILE"
# Format: "exclude DIR\\"
# Format: "exclude \\PATH\\FILE"
# Format: "exclude \\PATH\\DIR\\"
exclude Thumbs.db
exclude \\$RECYCLE.BIN\\
exclude \\System Volume Information\\
exclude \\Diskeeper\\
exclude \\Windows Backups\\
exclude \\Incoming Torrents\\
# Defines the block size in kibi bytes (1024 bytes).
# Default value is 256 -> 256 kibi bytes -> 262144 bytes
# Format: "block_size SIZE_IN_KiB"
block_size 128
I use a 128K block size in SnapRaid, cause I think I have enough RAM to handle it (and it would limit the space lost if I correctly understood)
I currently have about 5To of Data spared non-uniformly at all on the data disks: i.e. 2 data disks are almost empty, while two others are almost full (I keep about 200Go free on each disk). I guess this is not optimal from a performance point of view, but we'll see.
A snapraid -T on my system:
Code:
Compiled with gcc 4.5.1
Speed test with 4 disk and 262144 buffer size...
memset 1812 [MB/s]
MD5 252 [MB/s]
Murmur3 1116 [MB/s]
RAID5 int32x2 1692 [MB/s]
RAID5 mmxx2 1745 [MB/s]
RAID5 sse2x2 2481 [MB/s]
RAID6 int32x2 807 [MB/s]
RAID6 mmxx2 1304 [MB/s]
RAID6 sse2x2 787 [MB/s]
The new sync is running: console shows a steady 205-215 MiB/s for the moment.
I will report some performance benchs during the rebuilt.
Snapraid.exe process uses 1.6Go of RAM and an average of 45% of my little CPU power.
2 quick questions now, according to my detailed configuration:
_ Am I right to use a 128K block size in SnapRaid ? Any benfit to use 64K or 256K ?
_ Would I see a performance increase on the Snapraid syncronisation process by trying to "equalize" (can't find the damn word but I think you'll get the idea
) the data volume accross all my data disks ?
Thanks in advance for your answers, thanks again for your work !
Sorry for my english...
EDIT:
* 7% of the global syncronisation done for the moment: still sitting at 210 MiB/s according to the DOS console, but snapraid.exe RAM consumption has dropped to about 350 Mo.
* 45% done so far: 222MiB/s now, snapraid.exe still uses 45% of my CPU and about 350 Mo RAM.
* 86% : 188 MiB/s. snapraid.exe only takes 30% of my CPU now.
* 100% ! : 170 MiB/s finally and about 8 hours.
