Thursday, September 7, 2017

More SSD Lessons from Adam Albrec

(The following is a guest post by PPC Media Center creator Adam Albrec who shares his experience using SSD and SATA for a year on his MDD Power Mac.)

[UPDATE]: Adam has some very interesting additions to this post here: How to use an SSD in a PowerMac - Addendum. [END UPDATE]

So after 1 year using an O.W.C. SSD (and figuring out a SATA connection to make it go) what have I learned?

Still Loving it. For anyone doing PPC (in a case that lets you tinker), and wants a boost, in the final analysis, it is SO worth your money! My PPC is more responsive than my Brother's Mac Pro (Quad Xeon) and while it cannot say - convert a DVD to mp4 as fast, his only about 4x faster; which is interesting since it should theoretically have 15-20x the power of my MDD. Multitasking in Tiger also is silky smooth even with LOTS open.

So what's the downside or catch??

1. Well - a couple of very real things. This drive (especially in a 32Bit system like my G4) needs a good 60-80GB free for Swapping (especially if using a RAM heavy app like Photoshop CS4). Otherwise it will get REALLY unresponsive when it starts trimming unused blocks back to available status. With my current workload, just had to upgrade from 120GB to 240GB and now all is Right with the world and it's Super Happy again.

2. AND when first cloning a system to an SSD, it will be really SNOTTY for a couple of weeks while it gets sprawled-out. Most have noticed that when you clone OSX to a normal drive it will feel a bit laggy for a few weeks, but with an SSD, this turns into Kernel Panics - and lots of them for a week, then a few the 2nd week then after about a month smooth sailing. Apparently the RAID0/parallel-access that SSDs use can cause a lot of sync errors with the system bus until it balances and spreads over the drive. In practice this just reiterates the old adage in the beginning: “Save Often”, and after a few weeks you can relax.

Some have said that getting O.W.C.s Extreme 6G SSDs alleviate both of these concerns since they handle big chunks of data more efficiently and also reclaim unused blocks faster, but an OWC rep advised against it because he felt that syncing with a bus so much slower might lead to other problems (curious other people's experiences). With my system, this did make sense though as the 3G Electras they sell are virtually identical to my G4 systems native bus speed. For a G5, the Faster 6G SSDs might be better. At this stage, the prices are often within $10 for one or the other (NOTE: the 3Gs are warrantied for 3-years and the 6Gs for 5-years).

Now the SATA Question:

Have also upgrading to a Sonnet Tempo TSATA for the internal drives and a FirmTek 1Se2 eSATA card for external connections (like data recoveries and such) this too, has been AMAZING. With this configuration, and also a Sonnet Allegro FW800 card (still $20-$30 on eBay), I'm now able to copy/move files at TWICE the speed of my Brother's Hoity-Toity new Intel Beast!

And with Apple's new Thunderbolt to FW800 adapter (under $30), even our old machines can interface with Thunderbolt at about 75% of current real-world speeds for new systems. Only ultra high-end 6G systems really even make use of Thunderbolt fully, and the result is that our old Macs can be VERY COMPARABLE to USB3. This is especially useful to keep in mind if you are keeping an old G4 for a file server!

A real world use was recovering a PC Hard-Drive for a customer. Pulled 100GB of 'User's folder from an NTFS volume in 30-40 minutes (eSata to FW800)!!!!!

OK so now the 'BUT' on this topic...

There are things to keep in mind. The eSATA External 1se2 cards are still available new from FirmTek, but they are eSATA and for External drives (which is less ideal, than internal). The Sonnet cards built on the same chipset, are amazing, but very expensive and hard to find now (will likely take about 6-weeks of watching eBay and Amazon to find one).

But What about the inline IDE to SATA adapter cards many are using (as I did in the beginning)? They are lovely - especially for the $5 they cost. They work just fine (minus the ability to check SMART status of the drive), but only at IDE speeds. Until you find your FirmTek/Sonnet card, however, you'd be very wise to pick one up to start enjoying your new SSD right away. If you are only doing one System Drive, it might even make sense to stop there.

BUT the benefit of the FirmTek-based SATA/eSATA cards is that they have internal data-processing/buffering that accelerates and stabilizes file transfers between drives sharing the same card, well beyond the system bus-normal abilities (a big plus on a G4). So while I'm listening to iTunes, or watching a video and Carbon Copy Cloner comes on to do my backup, I don't even notice a hiccup in playback because both my SSD and Backup drive share the same Sonnet Card. On clocking a 1GB test-file transfer going from one drive to the other, it maintained a ROCK SOLID 52MB per second (416Megabits), and a MORE IMPRESSIVE 27MB per second (216Megabits) simultaneously copying in both directions - with NO additional overhead to the CPU!

Thus the Gold Standard would be to find the Ultra Rare 2-SATA/2-eSATA card by FirmTek (SeriTek/1VE2+2) and have any attached drives share this amazing performance boost.

But getting back to the inline IDE/SATA adapters, they are fantastic for using modern optical drives (little known fact, while you cannot connect two SATA drives with such adapters on an IDE ribbon-cable, since Sata doesn't have a Master/Slave framework, you can use an IDE drive as 'Master' and SATA as 'Slave', thus enabling having a normal Dual-Layer DVD+- Drive in the top and a Sexy New quad-layer, BlueRay/MDisc burner on the bottom of an MDD. And the upper and lower tray ejectors still work!

My current setup with the two cards is fine; transfers run about 45.5MB per second (364 Megabits), but when I am moving big files between an internal drive on one card and an external drive on the other card, or vice versa, and it has to go through the system bus, while still VERY fast, bus-saturation suddenly rears its ugly head and applications like iTunes start cracking and popping as it tries to keep up. The good news is that this really only seems to be noticeable during really big file transfers, rather than read-in data.

The two card solution does have one other issue worth mentioning. For the cards to function, they must have the same firmware (if both SeriTek based), and they DO NOT want to be seated next to each other.

And what of the "Other" cards like SIL3114/SIL3124? I have yet to get them to reliably work and stay working - after trying a lot of them. Maybe this isn't as much of a pill on some PowerMacs, but At least on Digital Audio through MDD, Apple's PCI Slots want it 'Their Way' and often don't work as expected. An advantage of the SeriTek cards is perfect compatibility (often in OS9 too).

So in short if you like your Apps, and just want better performance, it might make sense to switch your system drive to SSD and get some SATA love going to it.

Adam :0)

P.S. A final note on the Sonnet Allegro FW800 card: While ultra-big drives (larger than 2TB) are a big issue even for many newer systems, O.W.C. has a USB2/FW800 Dual Enclosure for under $100!

It supports 20TB drives in Striped, Mirrored and JOBD configurations and with the Sonnet Allegro is absolutely seamless to use.

https://eshop.macsales.com/item/OWC/MED3FR0GB/

Just note that OS9 will not recognize more than 2TB, and will try to “Initialize” the drive – so you've been warned! Also for compatible drives, OS9 will only run it at FW400 speeds.

When you see how much 'Real' raid cards still cost for these older systems used on eBay (usually only supporting OSX OR OS9), and see this unit flawlessly do the heavy lifting for a say a mirrored config, it is an amazing value. The normally Green lights will momentarily flash Red and rebuild blocks so fast you don't even notice during sometime sensitive - like video playback.

1 comment:

  1. OK have to post an additional (+) and (-) with the scenarios talked about previously.

    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.

    OK, no a bit of (-).
    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).

    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.

    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.

    Adam Albrec

    ReplyDelete