{Spam?} Re: Gem sucking whole CPU for no visible reason... intermitently WAS Re: [GEM-dev] Re: [PD-dev] oprofile - streamlining Pd/gem patch

[IOhannes m zmoelnig]

james tittle wrote:
> hey all,
> 
> ...then all you'd need to do is to [GEMglPushMatrix] before something 
> that would change that matrix, and [GEMglPopMatrix] 
> afterward...[separator] basically does this for three matrices at the 
> same time, at the beginning of it's Gem::render():  GL_COLOR, 
> GL_TEXTURE, & GL_MODELVIEW...these are then popped back in the 
> postrender() call...

so i am not really convinced that exchanging [separator] by an 
abstraction that does the pushing/popping will help you much.

> 
>> so I removed many of the separators from my patch and we'll see if that
>> improves things.
>>

yes, lots of them are just redundant. (e.g. you don't need to 
[separator] at the last outlet of a [t a ... a]

>> The patch seemed to be running fine before I put in [rubber], the
>> abstraction that contains the rubber stuff is [single-moment]. But now

it might be that you are experiencing a denormalization problem with 
[rubber] (but unklikely if you are on AMD)

mfg.dr
IOhannes