Currently Being ModeratedJan 1, 2013 8:11 PM (in response to Richie Hatch)
RE: moving Apps
I think this has been added to MacOS X over the last several versions and you are just seeing it now because you are doing more moving. I do not think this is a defect of any kind.
RE: slow SSD
How much File storage are you using on this SSD out of its actual capacity?
What steps have you taken to ensure that it does not immediately clog with deleted data?Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
Currently Being ModeratedJan 2, 2013 12:56 AM (in response to Grant Bennet-Alder)
Thanks for the reply Grant.
Before I did the system clone I deleted a lot of old unused Apps to make extra space on the SSD. Passwords where not asked for when doing this so something has changed with the SSD and permissions I think...???
As for space remaining on the SSD... I have used 97GB of a total of 209GB (256GB formatted).
I have yet to enable Trim support on the SSD but might do if I notice significant performance slips. I had read that its fairly optional anyway as the drive has its own 'Garbage Collection" so to speak...?
I notice you have a similar MacPro in your signature....? What are your startup times like?
Currently Being ModeratedJan 2, 2013 6:55 AM (in response to Richie Hatch)
The traditional way an Operating System deals with "deleted" files is to remove ONLY the Directory information and simply add the data blocks to the free pool. Those "deleted" data blocks are not cleared.
This works in rotating drives because:
1. The logical block size is the same or larger than the physical drive block size.
2. Rotating magnetic media are block-for-block re-writable.
In SSDs physical blocks are much larger "superblocks", and re-writing a portion of a superblock is a slow and difficult read-modify-write operation. In addition, since the OS did not notify the drive what data are no longer needed, deleted data continue to be carefully maintained and re-written by the drive. Soon every write operation becomes a read-modify-write, and performance deteriorates.
In my opinion, this nearly-full condition is likley to cause drive failure. Something more than wishful thinking is required.
Apple enables TRIM on the drives they install directly. They do not do so for third-party drives, but that is likely because those drives have not been tested by Apple.
I have been using a very small SSD as a boot drive for a while, and periodically consolidate free space followed immediately by erasing free space with a third-party utility. I believe this has kept me out of trouble. My son has been using SSD in his laptop and doing nothing for maintenece, and he has killed two drives in a year.
Trim Enabler utility from groths seems to be working, and makes things simple. Your mileage may vary.
if I notice significant performance slips
You added a much lower latency drive and startup times did not improve significantly. Much of the time required for startup is needed for memory testing. The rest is largely attributable to disk Read/Write times. What more evidence do you need?Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
Currently Being ModeratedJan 2, 2013 2:58 PM (in response to Grant Bennet-Alder)
Thanks for the reply. It turns out part of the problem was related to a Western Digital external Firewire Harddrive that I had attached. I disconnected that and restarted and it knocked almost 30 seconds off the startup time.
I have since enabled Trim from groths on your advise.