I have seen a few pages discussing this and some scripts that I won't run because I don't understand them, so would be great if the experienced users can share some tips or scripts (and perhaps explain exactly what they do). Thanks.
|
There's lame solution, but it helps a lot — throw hardware at it. OCZ Vertex or Intel SSD work beautifully. |
|||
|
|
|
One way to boot faster is to start less software. Try stuff like ServiceScrubber and Lingon. But, for heaven's sake, be careful. It's very easy to make this a quick way not to boot at all! Also, a file system that's very fragmented is slow. That mostly happens if it was/is very full, but may have other reasons. SSDs can be a solution if the hard drive speed is what's limiting you. |
|||
|
|
|
Maybe it's worth looking at why the boot time matters. One of the best features of Macs is the very functional, and more importantly very fast, sleep mode. The workstations at our company are all Apple, and they simply go to sleep every evening or after a period of inactivity. Even with network home directories and a directory server in play, it only takes 10-15 seconds to revive them from sleep. |
|||
|
|
|
Seriously, don't reboot. Just put it to sleep! Rebooting is so 90's. If you're on a desktop just do › Sleep, if your on a MacBook just shut the lid. If you're worried about security then turn on "require password after sleep" in Prefs › Security. |
|||||
|
Throw-Hardware-At-It-DepartmentSSDs clearly should be the fastest option; but their price/capacity point is still a bit painful vs. hard drives. for quite a bit less, you could look at upgrading to newer hard drives: current SATA drives are cheap, huge -- and often even the 5400rpm units are faster than original factory mechanisms as a function of higher data density, never mind moving up to 7200rpm gear. Not-Rebooting-Departmentin my own experience, OSX laptops sometimes don't always actually sleep when closed -- if there's a process hanging things up. a unnoticed modal dialog (e.g. a Save check triggered by a dirty document in a non-foreground app) is all it takes, I think. if/when that happens, one's battery carries on being drained without your necessarily being aware of it, which sucks if you are counting on having a predictable amount of remaining work-time later on without an AC connection. and it sucks even more if the battery runs completely flat:
Apple > Sleep appears to just go into low-power mode, vs. entering full-on hibernation [memory image written to disk, then a full controlled power-off]. the ability to actively specify Sleep/Suspend or Hibernate behavior is about the only thing I miss from Windows. for me, these two third-party utils have helped:
|
|||||
|