MY [incomplete] home folder is consuming 49GB. 46 of that 49 is in my ~/Library and specifically most of that space is MobileSync.That sounds high.
So basically, I have 95GB allocated, and 25GB free
MY [incomplete] home folder is consuming 49GB. 46 of that 49 is in my ~/Library and specifically most of that space is MobileSync.That sounds high.
MY [incomplete] home folder is consuming 49GB. 46 of that 49 is in my ~/Library and specifically most of that space is MobileSync.
… slow running OS X on a 5400 rpm drive via USB. …
Agreed, and if I am to keep these two drives seperate, I'll have to move my home folder.Documents, photos, music, video - these generally don't need to have the speed your solid state drive provides. The applications need it.
Agreed, and if I am to keep these two drives seperate, I'll have to move my home folder.
As it stands, the 46GB out of my 49GB of home folder data is not documents, images or music, but rather in ~/Library. While I can temporarily improve that by cleaning the cache folder, that will eventually start filing up
View attachment 641916
No question, most of that is the backups found in mobilesync. I not only back up my iPhone, but also my kids on my machine. I think that adds up to a lot space.That's a lot in Application Support.
No question, most of that is the backups found in mobilesync. I not only back up my iPhone, but also my kids on my machine. I think that adds up to a lot space.
I doubt it, but I can google it.Can you redirect where that back up is being stored?
I doubt it, but I can google it.
I doubt it, but I can google it.
I suspect, it can be resolved if I move my home folder to the spinning drive.
At this point, I'm not sure. This was done more of a proof in concept and see how I feel. I think the overall difference is keeping the OS and apps on the SSD, so unlike the Fusion logic that will move data blocks on and off the SSD, I'll be keeping what's on the SSD, fairly static - provided I keep this arraignmentDo you get the feeling that you are doing manually that which Fusion does automatically and with far better granularity?
When the dust settled, I found I was facing only 25GB of free space on the SSD, and that's with only a tiny portion of my home folder on the SSD. I could not have my music, pictures, and documents, and download folder on the SSD, and even so my library folder is still sucking up 48GB of space - most of that is iPhone backups (I not only have my iPhone being backup on my machine, but also my two daughter's).=
At this point, I'm not sure. This was done more of a proof in concept and see how I feel. I think the overall difference is keeping the OS and apps on the SSD, so unlike the Fusion logic that will move data blocks on and off the SSD, I'll be keeping what's on the SSD, fairly static - provided I keep this arraignment
When I get home from work, today, I'll move the home folder and and give it a bit of time to see if this setup works for me. I'm not entirely sold that it will. I think letting Fusion do the work and only have one logical volume makes a lot of sense.
One suggestion ... if you don't mind a bus powered external SSD Velcro'd on your iMac stand, would be to put your OS, apps, etc. on the internal boot SSD, and then have your home directly on the external SSD (which would still be pretty fast), and use the hard disk for backup or for static libraries (music, video, etc). With the lower SSD prices available now, you could put a 1TB SSD externally, have your OS stuff internally, and the 2TB hard disk would make a nice Time Machine backup for it all ... plus you would still have the look and feel of an all-in-one iMac.
As I mentioned in another thread on this topic, I would just like for Apple to allow us to configure separately how big of an SSD goes into Fusion Drive. My current set up is with a 512GB ssd fused to a 1TB hard disk and that is perfect.
Yeah ... I too have wished for BTO options to select the SSD and Hard Disk separately and then the user could decide how they wanted to use them and whether to make Fusion drives or not (or partially ... I like to have my Windows boot on a SSD partition, with the rest of the SSD and hard disk in a Fusion volume. It would then be necessary to have the Fusion commands in DiskUtility or somewhere to be easy ... but the Terminal commands are easy enough for now.And, how about giving us the option in System Preferences to fuse or unfuse drives?
… option in System Preferences to fuse or unfuse drives?
Yeah, good point, I was wondering about that. I messed up moving my home folder last night. I was trying to do two things at once that didn't work. I'm now restoring my CCC backup to get the system back to the way it was.I suspect having your home folder on the SSD will be beneficial due to frequent access to the data libraries stored there.
Good suggestion, I'll go and do that.Move the MobileSync (iOS backups) folder to your hard drive, and symlink it back to where it was. There's no reason to have iOS backups on your SSD.
The time spent pondering the optimal storage setup, moving data, managing files as usage patterns and OS versions change in addition to capacity management, and the backup/restore cycle to try Fusion vs unFusion is IMHO at least 100x higher than the time saved, perceived or real, for splitting SSD & HD partitions apart.Yeah, good point, I was wondering about that. I messed up moving my home folder last night. I was trying to do two things at once that didn't work. I'm now restoring my CCC backup to get the system back to the way it was.
Good suggestion, I'll go and do that.
I agree, the time savings is not there, but then I wasn't going into this to unfuse the drive, but rather I needed to restore my system, and I already had a backup, so since I was already going to do a restore, why not.IMHO at least 100x higher than the time saved
By all means, I wasn't trying to be critical of you trying it. I have done so in the past. I've worked years in data storage and optimizing user experience for large corps. The Fusion drive algorithms were not invented at Apple, but is the 1st consumer level storage tiering implementation tmk that's been around for decades in the enterprise storage world. On other Un*x platforms it's generically known as LVM + LVG aka HSM. A decent primer on how this works can be found on SNIA's website: http://www.snia.org/sites/default/e...torman/LarryFreeman_What_Old_Is_New_Again.pdfI agree, the time savings is not there, but then I wasn't going into this to unfuse the drive, but rather I needed to restore my system, and I already had a backup, so since I was already going to do a restore, why not.
Either way, I was going to be spending time restoring my system, so why not try something different and see if this improves my user experience?
I've stated in this thread and elsewhere, that I have some misgivings on the benefits of splitting up the Fusion drive, but as they say, nothing ventured, nothing gained. I'm willing to spend some time to hashing this out and see if there's an improvement.
I agree with you, however Apple has done a good job with Fusion and I was happy with it, but I'm willing to try something different.
Another hidden disadvantage to Fusion drive is that as the above post states, everything is written to the SSD first.The bottom line for me is that with Fusion Drive, 99% of the time the computer is writing data, it is going to the SSD. That, plus the time savings of not having to fiddle around with where to keep stuff, vastly outstrips the non-Fusion set up for me.
As I mentioned in another thread on this topic, I would just like for Apple to allow us to configure separately how big of an SSD goes into Fusion Drive. My current set up is with a 512GB ssd fused to a 1TB hard disk and that is perfect.