On Mon, Aug 24, 2009 at 6:05 AM, Florian Bösch <[email protected]> wrote:
> On Aug 24, 5:07 am, mclovin <[email protected]> wrote: > > Anyways, I am just horribly dissappointed by Pyglet. I used it for > > about a year and always just excused some of its performance lags > > because it was a scripting language. but a scripting language in a > > browser kicks Pyglet's *$$ > > It's not pyglets fault really. > 1) ctypes FFI calls are slow > 2) Chrome JS isn't really a "script" language, it gets compiled down > to x86/x64 machine code QFE. V8 is one of the most heavily optimised interpreters on the planet, and cuts a lot of corners - thus why it only runs on x86 machines. However, 7500 particles is not so much. Doing the draw loop in C I get > to 20'000 particles @ 60FPS. See http://codeflow.org/particles.tgz, > which in essence is I had to switch that to vertex arrays to achieve that sort of performance on my integrated card - it might perform even better on your system like that. -- Tristam MacDonald http://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
