Pygame using more CPU resources could be completely expected because it uses software rendering while Pyglet/rabbyt would be using openGL (i.e. hardware)
Also, because pygame basically requires you to write your own main loop (although it provides facilities to help), it's fairly easy to write loops that use more cpu than others. In my experience, I use OpenGL with pygame and have my own little dynamic framerate thing and get nice low CPU usages most of the time. On Thu, Jul 31, 2008 at 3:42 PM, Python Nutter <[EMAIL PROTECTED]>wrote: > I was annoyed by the OP's observations as well. I've converted my > program to many different Python game/media APIs to observe the > differences. > > Pygame = chew up the most CPU resources > Pyglet = chews up 28% to 42% CPU (surprised that the low CPU use was > on old PowerPC G4 processors and the new latest Intel Core 2 Duo was > chewing up 42% on the same program/codebase) > Pyglet + Rabbyt = only 6%-8% CPU depending on old PowerPC G4, Intel > Celeron M, Intel Core 2 Duo, does not matter what the CPU, and *the > clear winner* for my use =) > >
