Maybe the right answer is "Don't do this in Gambit", but I'd like to give it a try:<br><br>I'm writing an application, in Gambit. It does OpenGL graphics. It runs at 100fps. It's interpreted.<br><br>
Now, put down the pitch fork -- the only thing it's doing at 100Hz is <br> for 20 different objects<br> glLoadIdentity<br> glPushMatrix<br> some rotation<br> glCallList<br> glPopMatrix<br><br>This works fine, _except_ when I get hit with a gambit gc, it costs me like 70ms ... which becomes a noticable lag in my otherwise smoothly rotationg screen.<br>
<br>What are my options? Can I get a thread local heap? My basic usage is the following:<br><br>launch gambit app<br> --> it opens up a glut window<br> --> it listens on port ABCDE for new graphics primitives<br>
<br>in my editor window, I type some code; I send new primitives to port ABCDE; my gambit app spends a bit of time building it into a new display list<br><br>That's all. What can I do in this particular situation?<br>
<br>Thanks!<br>