![]() I’m tempted to wipe the drive, reinstall the OS and restore from backup. ![]() I’ve never done a clean install of the OS on this machine - always just upgraded and installed patches when the App Store indicated it was time to do so. I also have some widgets in the task bar that show CPU and they certainly weren’t showing a CPU-bound system. The system behaved as though it were CPU bound but Activity Monitor (when it would come up) didn’t indicate any particular problems. Once today it took about 10 minutes for the system to shutdown so it could restart, with multiple apps causing the shutdown process to timeout and need to be force-quit. Often, once Finder starts doing this it seems to gradually disable the whole system. I can’t say whether it’ll ever get to the point where it returns to normal but it’s not looking likely. As I type, the system’s been up ~1 hour and, other than the initial 20 minutes post-restart, Finder’s been high. Rebooting seems to help for a while but then the problem eventually returns - around 20 minutes after restarting. While Finder does seem to have a large number of ports open (~1900) that doesn’t seem to change much when Finder’s CPU usage goes from next-to-nothing to ~30% and stays there. The ‘Memory Pressure’ graph in the ‘Memory’ tab in Activity Monitor shows a narrow green band at the bottom taking about 10% of the space. My typical setup seems to use around 5.5GB and cached files ~2.5GB, with little to no swap. It doesn’t appear to be a memory constraint problem, either, despite just 8GB RAM. During such times, overall CPU usage is split ~10% System, ~30% User and ~60% idle.Įxamining Finder's open files & ports doesn't give me much of a clue but it mainly seems like basic system stuff and there are no hints therein as to other programs or processes that might be driving this behaviour. More than 95% of the time, though, Finder will be ~30%. Once it starts consuming ~30% of CPU, Finder will occasionally drop right down to low single figures usage but only for 5 or 10 seconds before it goes right back up to 30%. 10-15% when Finder is at 30% and 1% when Finder’s at 2%). While it's doing that (and I'm not doing much else on the iMac) there are no other processes with comparable usage, though WindowServer is typically in the top three, running at around 1/2 to 1/3 of Finder’s usage (i.e. Until then, though, I'd like to try to understand why Finder spends significant amounts of time - but not always - running at around 30% of CPU (according to Activity Monitor). That may well solve this problem or make it disappear (I certainly hope so). It's had 8GB RAM since I got it (new) and I've just ordered more so I'll have 16GB (max) soon. I'm on an old iMac (Late 2009) and High Sierra is as far as it can go in terms of OSX (even going this far has proved to be a problem due to the assumptions the OS designers make about typically-available system resources :( ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |