SSD RAID0 FC > TRIM?

[ParadokS]

My system: GA-P55-UD5 (ICH10R) / i5 / 8GB DDR2 dual channel / SSD X25-M80GB G2

I plan to get another cheap X25-M 80GB and run them in RAID0 cause I need the extra space - namely STEAM games take A LOT of space. But since OS doesn't usually take more than ~20 GB it doesn't really work to run them in regular AHCI. I would have 60GB free on first drive, but i need ~100+.

We know by now that running SSD in RAID0 removes the TRIM function, which reduces drive performance over relatively short time (matter of months). This can be circumvented by using some image/clone backup of your OS RAID array, stripe the ARRAY and secure erase the drives, re-create the array and use bootable USB stick to recreate your OS image/clone.

Reading through various forum threads I get the impression FC can help with this somewhat, to delay the need for this procedure - compensate the missing TRIM if you will. But I have not found a definite guide/how-to/suggestion thread regarding this issue.
I did however read somewhere that FC uses block-level cache and not file level cache as windows uses - but block level is highly volatile and can cause data corruption and other nasty stability/reliability issues

Perhaps some users here with some experience running SSD RAID0 arrays using this product to help compensate for TRIM could jump in with a few tips or advice
I had an idea to possibly use a ram drive for various things like temp/cache folders used by windows/chrome/pagefile etc.

Unless FC could noticeably help prolong the periods between SE/image of OS on a RAID0 then it might not be worth it.

[BikeHelmet]

Have you looked into Link Shell?

1) Just pick a folder on SSD1, then move it to SSD2. (C:/Programs/Steam/SteamApps/Common/GameName to D:/Games/GameName, for example)
2) Right-click the folder and choose Pick Link Source.
3) Go back to the original location.
4) Right-click in a blank spot, then choose "Drop As -> Junction"

You're done. The folder is on your new SSD, but your OS still thinks it's on your first one.

I do this all the time to link games to my Steam folder. Favourite games go on my SSD, the rest on my HDD.

[ParadokS]

That's pretty brilliant
With this I could keep my TRIM - perhaps even boost the performance with FC, now compensating for the lack of RAID0 instead - and still utilize the full capacity of both SSD drives, eventhough my STEAM folder requires to be in "one" location.
Looking briefly at the link it looks quite complicated though, but I'll get some breakfeast and a shower first then I'll take a look at it

Thanks for the link

Although I am still interested in what people think about my original questions. Will the FC prolong the secure erase/re-imaging process on a SSD RAID0

PS: Remember this linking business doesn't work with mapped network drives or mounted folders. From what I gather it only works on local harddrives.

[BikeHelmet]

If you turn on write cache with a high write latency, that'll certainly help SSD lifespan.. It'll catch many repeat writes and store them up, then only commit once. It may also allow the OS to store up a bunch of smaller writes and deliver them to the SSD in a more sequential fashion. Actually, that's fairly likely if a program reads or writes sequentially. Different programs will still want to manipulate different blocks, but even so I'm sure there'll be some benefit.