| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <b5eb567d-9866-8f0f-ea61-83ae97d4d21f@molgen.mpg.de>
Date: Fri, 2 Apr 2021 11:09:53 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: linux-raid@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: OT: Processor recommendation for RAID6
Dear Linux folks,
Am 08.04.19 um 18:34 schrieb Paul Menzel:
> On 04/08/19 12:33, Paul Menzel wrote:
>
>> Can you share your experiences, which processors you choose for
>> your RAID6 systems? I am particularly interested in Intel
>> alternatives? Are AMD EPYC processors good alternatives for file
>> servers? What about ARM and POWER?
>>
>> We currently use the HBA Adaptec Smart Storage PQI 12G SAS/PCIe 3
>> (rev 01), Dell systems and rotating disks.
>>
>> For example, Dell PowerEdge R730 with 40x E5-2687W v3 @ 3.10GHz,
>> 192 GB of memory, Linux 4.14.87 and XFS file system. (The processor
>> looks too powerful for the system. At least the processor usage
>> is at most at one or two thread.)
>>
>> ```
>> [ 0.394710] raid6: sse2x1 gen() 11441 MB/s
>> [ 0.416710] raid6: sse2x1 xor() 8099 MB/s
>> [ 0.438713] raid6: sse2x2 gen() 13359 MB/s
>> [ 0.460710] raid6: sse2x2 xor() 8910 MB/s
>> [ 0.482712] raid6: sse2x4 gen() 16128 MB/s
>> [ 0.504710] raid6: sse2x4 xor() 10009 MB/s
>> [ 0.526710] raid6: avx2x1 gen() 22242 MB/s
>> [ 0.548709] raid6: avx2x1 xor() 15406 MB/s
>> [ 0.570710] raid6: avx2x2 gen() 25699 MB/s
>> [ 0.592710] raid6: avx2x2 xor() 16521 MB/s
>> [ 0.614709] raid6: avx2x4 gen() 29847 MB/s
>> [ 0.636710] raid6: avx2x4 xor() 18617 MB/s
>> [ 0.642001] raid6: using algorithm avx2x4 gen() 29847 MB/s
>> [ 0.648000] raid6: .... xor() 18617 MB/s, rmw enabled
>> [ 0.654001] raid6: using avx2x2 recovery algorithm
>> ```
[…]
> Maybe some more data. AVX512 from Intel processors really seems to
> make a difference in the Linux tests. But also
>
> ### Intel Xeon W-2145 (3.7 GHz) with Linux 4.19.19
>
> ```
> $ dmesg | grep -e raid6 -e smpboot
> [ 0.118880] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
> [ 0.379291] smpboot: CPU0: Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz (family: 0x6, model: 0x55, stepping: 0x4)
> [ 0.398245] smpboot: Max logical packages: 1
> [ 0.398618] smpboot: Total of 16 processors activated (118400.00 BogoMIPS)
> [ 0.426597] raid6: sse2x1 gen() 13144 MB/s
> [ 0.443601] raid6: sse2x1 xor() 9962 MB/s
> [ 0.460602] raid6: sse2x2 gen() 16863 MB/s
> [ 0.477606] raid6: sse2x2 xor() 11425 MB/s
> [ 0.494609] raid6: sse2x4 gen() 19089 MB/s
> [ 0.511613] raid6: sse2x4 xor() 11988 MB/s
> [ 0.528614] raid6: avx2x1 gen() 26285 MB/s
> [ 0.545617] raid6: avx2x1 xor() 19335 MB/s
> [ 0.562620] raid6: avx2x2 gen() 33953 MB/s
> [ 0.579624] raid6: avx2x2 xor() 21255 MB/s
> [ 0.596627] raid6: avx2x4 gen() 38492 MB/s
> [ 0.613629] raid6: avx2x4 xor() 19722 MB/s
> [ 0.630633] raid6: avx512x1 gen() 37621 MB/s
> [ 0.647636] raid6: avx512x1 xor() 21017 MB/s
> [ 0.664639] raid6: avx512x2 gen() 46859 MB/s
> [ 0.681642] raid6: avx512x2 xor() 26173 MB/s
> [ 0.698645] raid6: avx512x4 gen() 54210 MB/s
> [ 0.715648] raid6: avx512x4 xor() 28041 MB/s
> [ 0.716019] raid6: using algorithm avx512x4 gen() 54210 MB/s
> [ 0.716244] raid6: .... xor() 28041 MB/s, rmw enabled
> [ 0.716648] raid6: using avx512x2 recovery algorithm
> ```
>
> ### AMD EPYC Linux 4.19.19 (up to 2.6 GHz according to `lscpu`)
>
> ```
> $ dmesg | grep -e raid6 -e smpboot
> [ 0.000000] smpboot: Allowing 128 CPUs, 0 hotplug CPUs
> [ 0.122478] smpboot: CPU0: AMD EPYC 7601 32-Core Processor (family: 0x17, model: 0x1, stepping: 0x2)
> [ 0.364480] smpboot: Max logical packages: 2
> [ 0.366489] smpboot: Total of 128 processors activated (561529.72 BogoMIPS)
> [ 0.503630] raid6: sse2x1 gen() 6136 MB/s
> [ 0.524630] raid6: sse2x1 xor() 5931 MB/s
> [ 0.545627] raid6: sse2x2 gen() 12941 MB/s
> [ 0.566628] raid6: sse2x2 xor() 8173 MB/s
> [ 0.587629] raid6: sse2x4 gen() 13089 MB/s
> [ 0.608627] raid6: sse2x4 xor() 7318 MB/s
> [ 0.629627] raid6: avx2x1 gen() 15164 MB/s
> [ 0.650626] raid6: avx2x1 xor() 10990 MB/s
> [ 0.671627] raid6: avx2x2 gen() 20316 MB/s
> [ 0.692625] raid6: avx2x2 xor() 11886 MB/s
> [ 0.713625] raid6: avx2x4 gen() 20726 MB/s
> [ 0.734628] raid6: avx2x4 xor() 10095 MB/s
> [ 0.739479] raid6: using algorithm avx2x4 gen() 20726 MB/s
> [ 0.745479] raid6: .... xor() 10095 MB/s, rmw enabled
> [ 0.750479] raid6: using avx2x2 recovery algorithm
> ```
>
> Are these values a good benchmark for comparing processors?
After two years, yes they are. I created 16 10 GB files in `/dev/shm`,
set them up as loop devices, and created a RAID6. For resync speed it
makes difference.
2 x AMD EPYC 7601 32-Core Processor: 34671K/sec
2 x Intel Xeon Gold 6248 CPU @ 2.50GHz: 87533K/sec
So, the current state of affairs seems to be, that AVX512 instructions
do help for software RAIDs, if you want fast rebuild/resync times.
Getting, for example, a four core/eight thread Intel Xeon Gold 5222
might be useful.
Now, the question remains, if AMD processors could make it up with
higher performance, or better optimized code, or if AVX512 instructions
are a must,
[…]
Kind regards,
Paul
PS: Here are the commands on the AMD EPYC system:
```
$ for i in $(seq 1 16); do truncate -s 10G /dev/shm/vdisk$i.img; done
$ for i in /dev/shm/v*.img; do sudo losetup --find --show $i; done
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/loop4
/dev/loop5
/dev/loop6
/dev/loop7
/dev/loop8
/dev/loop9
/dev/loop10
/dev/loop11
/dev/loop12
/dev/loop13
/dev/loop14
/dev/loop15
$ sudo mdadm --create /dev/md1 --level=6 --raid-devices=16
/dev/loop{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15}
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
$ more /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
[multipath]
md1 : active raid6 loop15[15] loop14[14] loop13[13] loop12[12]
loop11[11] loop10[10] loop9[9] loop8[8] loop7[7] loop6[6] loop5[5]
loop4[4] loop3[3] lo
op2[2] loop1[1] loop0[0]
146671616 blocks super 1.2 level 6, 512k chunk, algorithm 2
[16/16] [UUUUUUUUUUUUUUUU]
[>....................] resync = 3.9% (416880/10476544)
finish=5.6min speed=29777K/sec
unused devices: <none>
$ more /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
[multipath]
md1 : active raid6 loop15[15] loop14[14] loop13[13] loop12[12]
loop11[11] loop10[10] loop9[9] loop8[8] loop7[7] loop6[6] loop5[5]
loop4[4] loop3[3] lo
op2[2] loop1[1] loop0[0]
146671616 blocks super 1.2 level 6, 512k chunk, algorithm 2
[16/16] [UUUUUUUUUUUUUUUU]
[>....................] resync = 4.1% (439872/10476544)
finish=5.3min speed=31419K/sec
$ sudo mdadm -S /dev/md1
mdadm: stopped /dev/md1
$ sudo losetup -D
$ sudo rm /dev/shm/vdisk*.img
```
Powered by blists - more mailing lists