There's got to be something wrong there. I'm running it here on a 600 MHz iBook and top reports only 50% CPU, with the odd peak above that, but mostly lower. Within the visualizer, drawing code is run every 16ms, which is eons of time between operations in CPU terms. All rendering is done using direct pixel blasting straight into the window's pixmap, with only a port flush of the whole block left to the OS. Maybe Quartz Extreme is unhappy with it - I can't test QE 'cos this iBook doesn't support it. My only other Mac is a rather old G4 which also doesn't use Extreme. There is really very little else left for me to optimise - at the end of the day it has to render 31 x 2 x 24 + 48 * 2 (max) little rectangles every 16ms, which is going to need some CPU. That's 1,584 rectangles. Each one has to have its colour calculated, then the actual pixels need to be set. You can't get something for nothing.
Existing users, log in. New users, create a free account. Lost password?
Looks great! - Graham Cox
There's got to be something wrong there. I'm running it here on a 600 MHz iBook and top reports only 50% CPU, with the odd peak above that, but mostly lower. Within the visualizer, drawing code is run every 16ms, which is eons of time between operations in CPU terms. All rendering is done using direct pixel blasting straight into the window's pixmap, with only a port flush of the whole block left to the OS. Maybe Quartz Extreme is unhappy with it - I can't test QE 'cos this iBook doesn't support it. My only other Mac is a rather old G4 which also doesn't use Extreme. There is really very little else left for me to optimise - at the end of the day it has to render 31 x 2 x 24 + 48 * 2 (max) little rectangles every 16ms, which is going to need some CPU. That's 1,584 rectangles. Each one has to have its colour calculated, then the actual pixels need to be set. You can't get something for nothing.Reply to This
Tuesday, March 30 2004 @ 10:30 PM PST