5 ms·
For what it's worth, I'm running Snow Leopard (10.6.8) and I see the same sort of terrible performance the article describes. Though I did improve matters dras
by colomon 15y ago
For what it's worth, I'm running Snow Leopard (10.6.8) and I see the same sort of terrible performance the article describes.
Though I did improve matters drastically by telling mds not to index my (Linux) MP3 server and my Time Machine drive. That made it go from nearly unusable to just frequently annoying.
The other crazy thing I've been seeing is it routinely takes Chrome minutes to shutdown -- in fact, pretty much every time I try to reboot my MBP without shutting down Chrome first, the shutdown process times out trying to exit Chrome.
- obituary_latte 15y agoAh yes. The dreaded Chrome renderer never enderer. I too have experienced the Chrome issue enough that I don't even try to close it normally anymore. Force quit is the only way I exit Chrome. Thankfully, the restore tabs functionality works well.
- ricardobeat 15y agoI'm glad to see I'm not the only one. This drives me crazy every time.
- kirbysayshi 15y agoFirefox 12 does this too, on both my MB Pro and iMac. I think it has to flush so many caches that disk I/O just takes forever. This is purely conjecture, though.
- ticks 15y agoNot sure if it will help, but have you tried running Firefox's hidden profile manager and created a new profile? Firefox was horrible to run on OS X for me, it would drag the whole system down, but since changing to a new profile it has run like a dream and not reverted back.
- blacksmith_tb 15y agoCreating a new FF profile made a significant difference for me, too, when I did it recently (for the first time in a couple years). I suspect that will be true on any OS, if you do a fair amount of installing and removing extensions, user scripts, etc.
- cpeterso 15y ago"Vacuuming" your Firefox profile's .sqlite files also helps.