Oh come-on quit making us beg.
So how was it? Describe the behavior. Any Benefits?
It's been excellent. I pretty much followed
Patrick Stein's original tutorial under 10.8.2 and everything just came together as advertised. To date, I've filled 425GB of the Fusion Drive, with 325GB free, so the spinner is definitely in use, yet it feels as fast as I'd expect an SSD to be. Apologies for the unscientific analysis but it'll have to do, I'm afraid.
I also can't comment on improvements over a stock setup as I put my Fusion Drive together when I originally built my 4,1/5,1 hybrid Mac Pro.
Regarding some comments on the interwebs that a home-made Fusion Drive doesn't function correctly and is merely a static corestorage volume, I don't see such behaviour. I've just had a look at iostat while loading and running XCOM: Enemy Unknown. This game was installed on my system recently, long after I'd exceeded the SSD capacity, and yet all game and save data was loaded from the SSD, just as it should with a true Fusion Drive.
What detriments? Could you partition it?
I see two "identical" OS X HDD icons in the boot manager screen. Either will boot OS X, though, so it's not really a problem. I can't seem to use DiskWarrior on the system drive (it's OK on the storage drives) any more, even though I upgraded to the Fusion Drive-capable version. Again, it's not really a problem. If I have to do any really "deep" maintenance, I'll just nuke and restore from Time Machine.
One thing I noticed, the initial spotlight indexing took longer than usual, with the estimated time remaining changing quite significantly throughout. This makes sense if the files were being redistributed immediately after their restoration from Time Machine.
Regarding partitioning, I haven't tried post setup but I did manage to set up a working recovery partition by installing Mountain Lion 10.8.2 from a USB key onto the SSD prior to building the Fusion Drive. I then deleted and formatted the Mountain Lion partition, leaving the recovery partition untouched, and built the Fusion Drive using the entire HDD and the new partition on the SSD. Cmd-R at boot brings up the recovery drive, just as it should, although it doesn't appear in the boot manager screen. I've since repeated the entire process using the 10.8.3 installer in order to ensure adequate NVidia driver support for the GTX 680 on the recovery drive. Probably unnecessary, but you never know...
I can't comment on creating a Boot Camp partition within the Fusion Drive as, instead of booting Windows directly, I've set my system to call up GRUB on the MBR of a separate 250GB HDD partitioned for Windows and Linux. Obviously, neither Windows nor Linux can read the Fusion Drive but at least Windows behaves itself. Linux, not so much! Any time there's a new kernel built via the software update, GRUB will try (and fail) to make sense of the Fusion Drive, and would continue to do so until the heat-death of the universe if it were allowed to. I got round this by turning off the OS Prober and manually adding my Windows 7 partition details to the GRUB config. I forget the details. I've probably blanked them out to preserve my sanity...
I think that's about it. Enough?
