In GEM if you need lots of objects then try to avoid using a gemhead or separator for each.  The setup time for pushing and popping the matrix thousands of times starts to add up. 

Also, use a model so rather than compute and upload the geometry in immediate mode each frame a display list is called instead.

The fastest solution would be to write a custom object that wraps all of the functionality you need.

On Fri, Apr 11, 2008 at 10:46 AM, marius schebella <marius.schebella@gmail.com> wrote:
I tried that too, with a set of new patches and it was quite fast
(although I think not as fast as luagl), but I already have a lot of old
interactive object patches that I wanted to use. they have mouseover
handling and also store textinformation.
actually it is a question of performance. I want as many as possible
objects and need to find the fastest solution.
marius.