First off, ATTO is a lousy bench mark for SSDs, was developed for HDD, and worst yet it uses data that is highly compressable. Yes This is what manufs use as it it gives an inflated (Higher) number, espacially for SFxxxx based controllers based SSDs.
PS I use AS SSD, which was designed for SSDs, and uses compressed data for it's benchmark.
If your file that you transfered consisted of a File that does not compress then you will not get near advertized performance. To check transfer speed you need to transfer between SSDs not between a HDD and SSD. The do NOT scale, that is two drives do not = 2 x one drive, maybe 60% and as Number of drives goes up scaling decreasaes.
Raid0 will NOT improve an OS + program drive in terms of loading OS not loading Programs.
NOTE you have an AMD chipset, so NO TRIM now, nor in the near future (intel should be coming out with a driver to support passing trim when in a Raid0 config shortly.
Just posed this about 10 mins ago inresponse to a raid0 question
Quote
As jitpublisher, I used Raid0 in all my IDE system ever sense they incoprorated it on MBs. It was great, and I never lost a single drive. I still have an E6400 (OCed to 3.2) that uses raid0 (Sata HDDs). Keep it for the Kids to play on when they vist. Stopped using raid0 when I got my first SSD.
Raid0 still has a limited place, and that is if you do ALOT of work with large file structures.
By nature these files take a lot of space and SSD are generally to expensive for most, ie 500 gigs -> 1 TB space. The Newer HDDs, with their much higher magnetic domain density, and in many cases the higher failure rate than there older models means that you must use HDDs made to work with raid.
Trim support, is probably the biggest negative for raid0. However Intell should be releasing RST ver 11.5+ which is suppose to allow trim to pass when drive is a member of a raid set-up (Back of mind in a month or two). AND THIS only applies if using a intel chipset!!
Raid0:
.. Improves Sequencial performance, BUT this is the Least Important parameter for an OS + Program drive. It is the small 4K random performance that is IMPORTANT and raid0 does very little to no improvement on this catagory - HENSE Raid0 does Very little to improve performance on a OS + program drive.
.. The improvement in sequencial performance is why I stated it would boost performance when working with LARGE file structures - But here it is limited to the read and write portion - as NO in-program performance is not dependent on SSD, or HDD.
Side comment, One reason larger SSDs are faster than their smaller sibling, is that the larger SSD uses two Little brothers in raid0 internally. (other reasons also exsit).
I have NO need for SSDs in Raid0, and I think in the vast majority of users a larger SSD is more sensible. SSD speed and HDD speed have the same IN-PROGRAM performance, and gamers see No Improvement in FPS when game is running - SO Placinging SSDs in Raid0 would do What.... That Said, I'm not totally opposed to RAID0, when most usesage is with large files, such as enconding/converting large Vedio files (.vobs are 1 Gig files, blue-ray up to 40 gigs for a single file.), Very large spreedsheets, Cad/Cam drawings, and working with hundreds of them 10 meg Photo bitmaps/jpegs. - ALL these, unlike os and program files, are Very large sequencial files - even a "Small" 10 meg Photo is 2,500 sequencial clusters. For Raid0 stay away from SF based Controllers, Recommend the marvel M4, Samesung 830, and Intel 510 (510 uses the marvel controller - the 520 uses the SF controller. - My reasoning is not just from reliability, but SF controlled get high Seq marks because of compressing the data, if data is non-compressable, performance drops off considerably.
End quote: Ref
http://www.tomshardware.com/forum/284789-32-should-raid