When the card has to draw less pixels, a **larger** percentage of the time is spent sending commands from the CPU to the card.
When the window is tiny, the card is drawing fewer pixels, but the CPU has to send the **same** number of commands per
frame.
So are you saying Same number of commnds per frame + More pixels gives <= cpu utilization, as compared to Same number of commands per frame + less pixels ? Here my cpu utilization is a dramatic 80% when glxgears is a 3x3 inch window and 4% when glx gears is maximized full-screen at 1280x1024 res. Also when I hide the 3x3" glxgears window behind say my browser window i.e bring another app window to front, and glxgears is no longer visible, cpu utilization remains at 80% or more.
Could you please clarify ? I think you haven't explained everything thats on your mind or know. I think my graphics card GPU is kicking in when I maximize but inactive when minimized, something to do with the way X works. its a hunch ...
Each frame requires some number of commands be sent to the card, this uses N CPU time. On my box, a full-screen gears window gets 166 frames per second, and a super tiny window gets 6224 frames per second. What was saying in my previous post was that 6224*N > 166*N.
_______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
