tag:blogger.com,1999:blog-749559194818088720.post2453168043830095156..comments2024-02-20T06:53:10.484-08:00Comments on PPC Luddite: More SSD Lessons from Adam AlbrecDanhttp://www.blogger.com/profile/04700474277267739107noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-749559194818088720.post-66073644293541246602017-09-24T11:05:48.922-07:002017-09-24T11:05:48.922-07:00OK have to post an additional (+) and (-) with the...OK have to post an additional (+) and (-) with the scenarios talked about previously. <br /><br />Starting first with the (+), The other morning I had Carbon Copy Cloner pop-up to back-up my SSD to the Working-Storage drive, while I was listing to iTunes AND restoring an external drive via eSATA AND listing to iTunes (with TenFourFox open with 15+ tabs). Shockingly the system remained responsive and iTunes never even flinched during all the cross-talk of all 4-drives doing their thing - even across the main system bus. <br /><br />OK, no a bit of (-).<br />Yesterday, I edited 10-big tiff images in Photoshop CS, and a Fractalizing program called "S-Spline 2". The difference this time, for my normal workflow, was that I also used Photoshop CS4 and a noise remover that is part of the now freeware Nik software plugins. Still no problems. UNTIL - I ran an action in 32-bit color (HDR). So now memory-paging for all these apps started to really build up and while this wouldn't show in System Monitor, I was getting dangerously low on available (TRIMMED) SSD. It still felt normal, and worked fine, right up until I told it to sleep - which took a very long time to occur, and then no waking it was in a real funk as the drive was Trimming back all those blocks to available status. On booting to a 'Utility' partition, all the data is still readable and working fine and the drive checks out just fine, but now it will take as long as it takes to go back to usable mode. If this paging remains below a certain level, it never really becomes noticeable, but above that, the system can become really unresponsive until this maintenance is completed. Since this is a new drive, I suspect it is even worse as all the data is still in large contiguous chucks that can be more effected by this phenomenon. My previous, smaller SSD would do this in a much quicker amount of time as the data was spread much more evenly over the drive and take about 5 (10-minutes at worst).<br /><br />This does bring up a question though on using the SSD for Scratch. The only apps I have that lean this hard on paging are Photoshop CS (which really benefits from the SSD's faster read time) and CS4 (that has a much bigger scratch footprint, but doesn't really need the SSD as much because it's CPU usage is more efficient/faster). I'm thinking that from this point, I will leave CS as it is, since I often use it for smaller and quicker jobs, and place CS4's scratch disk on my 7,200RM Working-Storage drive. I'm thinking it was this 32-bit thing that really nailed it. For smaller usage (that leans on RAM) the paging will still occur as it is now, but when it starts going crazy on memory usage, it can lean on the conventional drive. <br /><br />The ALTERNATIVE (that I will try first) is to simply leave the system on/awake after such usage in a low-power state (using single-CPU/Nap in C.H.U.D.) and let the blocks Trim during the night. <br /><br />Adam Albrecartphotodudehttps://www.blogger.com/profile/14625170205541427471noreply@blogger.com