I am still testing and searching through the extremely limited documentation but I have a few things to add on the performance side.
Parity and dual parity use a journal disk even if a SSD is not set as a journal. All incoming writes are written to the journal disk before parity is calculated and written to the disks. That is the basis of the slow write speed being about equal to the speed of one drive.
The dedicated journal does not completely help write speed. I am using 120GB Intel 530's so I see 400-500MBs write speed over the network, HDD's are 12x 6TB Hitachi in dual parity. After ~120GB has been written with a 100GB journal created, file copies pause briefly while parity data is written. There is no gap created in the file copy progress window which is a bit misleading. Still it's not a deal breaker for me, it's rare that I move more than 40GB at a time.
Now I am testing how the pool handles being full. So far 10TB copied, 40TB to go. There is a lot of mixed information about a 75% usage limit where the pool can go offline preventing you from deleting data and only allowing more disks to be added as a solution. Not a situation I want to be in with a Supermicro
5018A-AR12L.