I'm running SETI@Home on one core of my macbook. Snow Leopard. If I let SETI@Home use the one core (100%) while my wife is trying to use the computer for real stuff like websurfing, she complains that it's bogged beyond usability. But there's a whole 'nuther 2ghz core sitting there for her to use! I can see it idling in Activity Monitor. Why is Snow Leopard boggable when you're pegging just one core?
Yes, I'll ask the SETI@home site forum too, but I figured this forum might know something that changed w/ Snow Leopard regarding process priority, etc.
Yes, I'll ask the SETI@home site forum too, but I figured this forum might know something that changed w/ Snow Leopard regarding process priority, etc.