|
|
Question : Problem: iMac G5 runs very slowly
|
|
I have an iMac G5: CPU - PowerPc G5 1.8GHz Memory = 2 GB OS X 10.4.11 It runs very slowly. When mousing over dock icons, it can take several seconds for the dock to respond. Switching between programs takes an incredibly long time. I have already tried the following: - optimized the disk - repaired permissions - removed everything from the desktop - run all tests in Tech Tool Pro 4 - everything passed Any suggestions will be appreciated. Thanks!
|
Answer : Problem: iMac G5 runs very slowly
|
|
This sounds a little like a memory leaking application to me. 2 gb is more than enough to run Os x tiger.How many widgets are you running? I assume this is all happening not when you are ripping mp3 or rendering video but in general use. Do you get a sense of what app is gobbling up your memory from activity monitor. if you are not afraid of terminal then the top utility can help you narrow it down. http://docs.info.apple.com/article.html?artnum=106415 The only detail that would make me more certain about suggesting a memory leaking app would be if, after a reboot, its response is more normative but it gradually slows down over the course of days weeks until it begins to crawl. If it is just always slow then maybe it could be a nicing issue. An app may be grabbing for your cpu time. You can renice using terminal commands or use this gui utility. http://mac.softpedia.com/get/System-Utilities/BeNicer.shtml The other thing you might look at is downloading mainmenu http://www.macupdate.com/info.php/id/17111 You could use this to clean out all the caches. While you are at it just run everything this suite offers. As far as the difference between free and inactive OS X keeps files in inactive memory in case the same app calls on it again bit if another app makes a demand it is released as if it were free. http://docs.info.apple.com/article.html?artnum=107918 It is only when the combination of low free and low inactive that indicates your total memory is too low. At the end, the cpu bursts, assuming just general use, makes me lean more towards a nicing issue. Early versions of Os x were more prone to this but maybe an older app is just being too demanding. You can use Top to watch this as well.
|
|
|
|