Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Fusion nightmare

B

benwiggy

macrumors 68020
Jun 15, 2012
2,381
193
Brian Y said:
Fusion doesn't give you any control at all.
Click to expand...
Ah. The myth of control.:p

OS X is controlling all sorts of things that people used to do manually in days gone by. And it does them better than anyone could. (More frequently, more in-depth.) And it lets me get on with actually using my computer for important things like watching videos of kittens, or cataloguing the human genome.

"Remember the days when you had to move files by hand between media of two different speeds..?"

That's now up there with allocating memory for applications; managing SCSI peripheral chains; making daily tape drive backups; and, since Lion, remembering to save files.
 
Last edited:
B

Brian Y

macrumors 68040
Oct 21, 2012
3,776
1,064
benwiggy said:
Ah. The myth of control.:p

OS X is controlling all sorts of things that people used to do manually in days gone by. And it does them better than anyone could. (More frequently, more in-depth.) And it lets me get on with actually using my computer for important things like watching videos of kittens, or cataloguing the human genome.

"Remember the days when you had to move files by hand between media of two different speeds..?"

That's now up there with allocating memory for applications; managing SCSI peripheral chains; making daily tape drive backups; and, since Lion, remembering to save files.
Click to expand...

We're all allowed out opinion - me included. Okay?
 
G

gnopx

macrumors newbie
Original poster
Feb 16, 2013
14
0
my problem is photoshop scratch file, i need it to be on ssd, it's created by PS on every app launch and grows often to 50gigs

this cause my fusion hating, because i need 60gigs free on my ssd for PS scratch.

there are only two ways.

1) Un-fusion the drives (not officialy supported by apple)

2) partition the fusion in 186-942 (officialy supported by apple) and use the first partition for os & apps (60gigs maximum) to keep 60gb of ssd free. (60gb of hdd are wasted but it's a minor cons.
 
B

benwiggy

macrumors 68020
Jun 15, 2012
2,381
193
gnopx said:
my problem is photoshop scratch file, i need it to be on ssd, it's created by PS on every app launch and grows often to 50gigs
this cause my fusion hating, because i need 60gigs free on my ssd for PS scratch.
Click to expand...
1. Are you sure you NEED the scratch file on the SSD? Have you got any performance data suggesting that Fusion will hinder Photoshop?
Traditionally, best performance advice for PS scratch is to put it on a different volume from your system. So that would be your 5400rpm HDD in a non-Fusion setup.

2. Are you sure that you need ALL of the scratch file on the SSD?
Fusion can allocate blocks of the scratch file to different devices. So you may get the most frequently used blocks on the SSD anyway.

3. Are you sure that Fusion drive WON'T allocate the scratch file to the SSD, if that's something you do regularly?

I'm not saying that Fusion is a universal panacea, but I think it's important whenever any new technology comes along to check that any assumptions about it are true. I've been using Creative Suite 6 solidly, with over 200Gb on the volume, and I've not seen any evidence of any slowness by the HDD being called into service.
I would at least try it for a while before you split it.
 
Last edited:
philipma1957

philipma1957

macrumors 603
Apr 13, 2010
6,365
249
Howell, New Jersey
benwiggy said:
1. Are you sure you NEED the scratch file on the SSD? Do you need the high speed retrieval and storage rates of SSD for what is a form of virtual memory?
Have you got any performance data suggesting that Fusion will hinder Photoshop?
Traditionally, best performance advice for PS scratch is to put it on a different volume from your system. So that would be your 5400rpm HDD in a non-Fusion setup.

2. Are you sure that you need ALL of the scratch file on the SSD?
Fusion can allocate blocks of the scratch file to different devices. So you may get the most frequently used blocks on the SSD anyway.

3. Are you sure that Fusion drive WON'T allocate the scratch file to the SSD, if that's something you do regularly?
Click to expand...



If he had a diy fusion with a big ssd he would get what he needs from fusion. my complaint with fusion is apple does not offer a choice of ssd size 128 ssd 256 ssd 512 ssd all with a 1tb hdd should be offered.


Apple offers 4gb ram 8gb ram and 16gb ram which are super easy to diy .

They should offer the 3 ssd sizes for fusion which are not easy to diy.
 
Mike in Kansas

Mike in Kansas

macrumors 6502a
Sep 2, 2008
962
74
Metro Kansas City
gnopx said:
my problem is photoshop scratch file, i need it to be on ssd, it's created by PS on every app launch and grows often to 50gigs

this cause my fusion hating, because i need 60gigs free on my ssd for PS scratch.

there are only two ways.

1) Un-fusion the drives (not officialy supported by apple)

2) partition the fusion in 186-942 (officialy supported by apple) and use the first partition for os & apps (60gigs maximum) to keep 60gb of ssd free. (60gb of hdd are wasted but it's a minor cons.
Click to expand...

This would be a GREAT experiment to see how core storage handles the scratch file. I'm not familiar enough with PS to know how the file is created, named, over-written, etc. But it would be interesting to see how FD manages the scratch file(s) if you install PS on a non-partitioned FD arrangement. If they are accessed enough, they could/should get moved to the SSD portion of the array. If they get erased each time you close the app, it may have to "re-learn" over time; however, if the same file it written to time and time again, it may get moved.

Would you consider running this experiment? You can install everything on FD with no partition, run it for a while & record your results, and then do the same thing with a partitioned FD arrangement. If you either have iStat Menus, or download and install it for the 2 week free trial, you can see the independent I/O of each drive within the FD array. When I launch apps, I can look at the disk activity history to see where that app, or portions of that app, reside - SSD, HDD or both.

----------
philipma1957 said:
If he had a diy fusion with a big ssd he would get what he needs from fusion. my complaint with fusion is apple does not offer a choice of ssd size 128 ssd 256 ssd 512 ssd all with a 1tb hdd should be offered.


Apple offers 4gb ram 8gb ram and 16gb ram which are super easy to diy .

They should offer the 3 ssd sizes for fusion which are not easy to diy.
Click to expand...

Agree. And they may with the next iteration. I'm sure you have been following Apple hardware for quite a while, as have I, and you surely see their pattern in continual incremental improvement over time. It's what keeps us wanting to buy "next year's model" when "this year's model" would still be fine for 4+ years down the road! They never offer up the best solution initially - they eek it out over a period of time.
 
philipma1957

philipma1957

macrumors 603
Apr 13, 2010
6,365
249
Howell, New Jersey
Mike in Kansas said:
This would be a GREAT experiment to see how core storage handles the scratch file. I'm not familiar enough with PS to know how the file is created, named, over-written, etc. But it would be interesting to see how FD manages the scratch file(s) if you install PS on a non-partitioned FD arrangement. If they are accessed enough, they could/should get moved to the SSD portion of the array. If they get erased each time you close the app, it may have to "re-learn" over time; however, if the same file it written to time and time again, it may get moved.

Would you consider running this experiment? You can install everything on FD with no partition, run it for a while & record your results, and then do the same thing with a partitioned FD arrangement. If you either have iStat Menus, or download and install it for the 2 week free trial, you can see the independent I/O of each drive within the FD array. When I launch apps, I can look at the disk activity history to see where that app, or portions of that app, reside - SSD, HDD or both.

----------



Agree. And they may with the next iteration. I'm sure you have been following Apple hardware for quite a while, as have I, and you surely see their pattern in continual incremental improvement over time. It's what keeps us wanting to buy "next year's model" when "this year's model" would still be fine for 4+ years down the road! They never offer up the best solution initially - they eek it out over a period of time.
Click to expand...

right on spot. I have seen this time and time again.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom