just looked at the Avarage Disk Queue perfomance counter during image import/sync and preview buit. So if I put catalog on second drive it will be overloaded while third drive containing cache almost all the time did nothing.
So I decided to leave System drive just for system and put catalog on third drive as well as cache, photos remain on second. May be it's sound strange but there is more workload on disk with photos itself during reading and then CPU load to built preview, because RAW file around 40-50 MB each and preview less then 10.
And as third drive have 32 MB cache (may be even 64? don't rememeber) and photo previews built one by one, it's not big deal to write it to the drive once ready. For sure having SSD for system and catalog is better solution, I have such in my leption, but that is sister's PC and I'm not planning to upgrade it soon.
Regarding RAID - it's pain if you would like to reorganize it and especially if that's hardware raid, you will depend on controller (built into motherboard or PCI-Express) so I'm scared to create RAID5 (easier to manage data, but slower write speed) or RAID0 (I've recently lost my temp drive wich used RAID0, not big deal but anyway I was not happy to spend another few days on reorganizing data)
For anyone who are planning to have some redundancy I found almost perfect solution: WD MyBook with USB 3.0 and 1Gb Ethernet connection and have one disk up to 4TB. As for better redundancy you should have data in two separaty physical locations (it's better then have just mirrored drive on one PC) so Ideally I would by two of them and install at my home and sister/mother home, then configure only photo sync and have catalog on my laptop on SSD (sister will have her own catalog as well locally on the PC). I'm not going with this way as I already spent money on internal hard drives and good external USB 3.0 box cost about 50$ which is half of 2TB drive price.