 |
 |
Bad for OSX?
|
|
|
|
|
Forum Regular
Join Date: Sep 2000
Location: Michigan, USA
Status:
Offline
|
|
I run SETI 24/7 on my MDD tower. The CPU's are almost completely maxed out, according to CPU Monitor.
I remember reading (I think on MacNN forums) a long time ago that OSX uses the CPU during "idle time" (when the CPU's aren't being used to their fullest) to perform some sort of system maintenance.
Is this true? Am I causing damage to the stability of my system by maxing out the processors 24/7 and not letting this "maintenance" get done properly?
Just yesterday I had to hard reboot (using the button on the tower) because SOMETHING just wasn't right - many applications, including SETI - couldn't start, or process their preference files. First time it has happened.
|
|
MBP 17" Core i7 matte screen; iPad 16Gb 3G
|
| |
|
|
|
|
|
|
|
Moderator Emeritus  Join Date: Dec 2000
Location: College Park, MD
Status:
Offline
|
|
No.
OSX maintenance runs no matter what.
It runs at about 2AM, if I remember correctly.
Almost everyone here has their CPUs maxed 24/7 (what's the point of not using them?  ), and I know that at least for me, there are no problems.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Jan 2002
Location: Mile High City
Status:
Offline
|
|
Ditto here too. After months of running non-stop under OS-X, not a problem.
Your problem may have been caused by some other software issue. Since moving to OS-X, my only downtime has been the result of power outages.
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Sep 2000
Location: Michigan, USA
Status:
Offline
|
|
Great! I was hoping you would say that! 
|
|
MBP 17" Core i7 matte screen; iPad 16Gb 3G
|
| |
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Mar 2002
Location: Washington, DC
Status:
Offline
|
|
MacOS X, unlike MacOS 9, has preemptive multitasking. That is, the OS is not at the mercy of running programs -- in general -- and when it decides it's time to give another application a chance to run, it preempts the running application and gives a slice of time to the program waiting to run.
To see this in action for yourself, run Process Viewer (Applications/Utilities/Process Viewer) and then run something else that uses the CPU and see that it gets its share.
In fact, you can see that FAH has a "nice" value of 20, which means it only gets to run if nothing else needs the CPU at that moment. The 100% CPU utilization you see is really everything running that wants/needs to with FAH filling in the spare time.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top