Questions and Answers : Macintosh : Rosetta's CPU time is off on a G3 iMac
Author | Message |
---|---|
Jim Milks Send message Joined: 4 Aug 06 Posts: 5 Credit: 50,724 RAC: 0 |
I've recently set my 400 MHz G3 iMac to back to crunching on Rosetta work units after getting compute errors at Einstein. I've noticed that the CPU time runs very slowly. One second of CPU time takes 8-9 seconds of real world time. As a result, a work unit that has been crunching since yesterday afternoon is claiming that it's only taken 1:35:19 of CPU time when it's actually been crunching for >13 hours. Anyone have an idea what's going wrong? If it's just that a G3 iMac is too slow for Rosetta or has too little RAM (it only has 256 MB RAM), anyone know of a more suitable project for an old, slow Mac? Thanks. |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
More memory would definately be a good thing. It sounds like you are either waiting for memory to get any work done, or that there are other tasks running that need CPU. Rosetta runs at the lowest priority possible to allow other work to proceed as though it isn't there. Rosetta Moderator: Mod.Sense |
Jim Milks Send message Joined: 4 Aug 06 Posts: 5 Credit: 50,724 RAC: 0 |
More memory would definately be a good thing. It sounds like you are either waiting for memory to get any work done, or that there are other tasks running that need CPU. Rosetta runs at the lowest priority possible to allow other work to proceed as though it isn't there. I went looking for whatever was taking CPU time via the Activity Monitor utility, as I didn't have any other applications running. Turns out a weather widget had crashed and (for some reason) was taking 45% of the CPU. Once I forced the widget to quit, Rosetta started running much faster. |
Jim Milks Send message Joined: 4 Aug 06 Posts: 5 Credit: 50,724 RAC: 0 |
More memory would definately be a good thing. It sounds like you are either waiting for memory to get any work done, or that there are other tasks running that need CPU. Rosetta runs at the lowest priority possible to allow other work to proceed as though it isn't there. I went looking for whatever was taking CPU time via the Activity Monitor utility, as I didn't have any other applications running. Turns out a weather widget had crashed and (for some reason) was taking 45% of the CPU. Once I forced the widget to quit, Rosetta started running much faster. |
Questions and Answers :
Macintosh :
Rosetta's CPU time is off on a G3 iMac
©2024 University of Washington
https://www.bakerlab.org