Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'A possible fix for high Finder CPU usage' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible fix for high Finder CPU usage
Authored by: Diomedes on Apr 06, '10 02:18:40PM

I was wondering about this too. I took my mid-2009 MacBook Pro into my Apple Store because I noticed how slowly the Finder was responding, and I would get a beach ball when switching between Finder windows. My hard drive was indeed failing, but even after replacing it and doing a restore via Migration Assistant (so I would have a fresh copy of Snow Leopard), it was still happening. My MacBook Pro is a top-of-the-line Mac: 3.06 GHz processor, 8 Gb RAM, and 7200 RPM drive, and the nVidia GPU is on. So I didn't think there should be any reason why Finder should be slow on a new machine with a new hard drive.

Disabling calculate all sizes fixed the issue…amazing. I use Path Finder, which seems to calculate file/folder sizes instantly, with low CPU utilization and without taking up CPU or real memory.

I will say though: having ample RAM is a double-edged sword. It seems applications abhor a vacuum, and apps will use up more real memory and the same amount of virtual memory.

[ Reply to This | # ]