instruments

Member
Posts: 117
Joined: 2010.09
Post: #1
Hi all,

Thought I would spend some time profiling my code.
Decided to time profile opengl.
84% of the time seems to be taken by semwait_signal; whilst the rest of my game barely shows up (maybe 0.8% worst case).
I guess this is good?, and semwait_signal is some system call that I can't avoid?. I notice if I draw more eventually (obviously) the frame rate drops but semwait_signal is still top of the list.
What is it? :-)

Cheers
Quote this message in a reply
Luminary
Posts: 5,143
Joined: 2002.04
Post: #2
semwait_signal means your thread is blocked, doing nothing and taking no CPU time.
Quote this message in a reply
Member
Posts: 117
Joined: 2010.09
Post: #3
So is that good?????

Blocked by what??
Quote this message in a reply
Luminary
Posts: 5,143
Joined: 2002.04
Post: #4
It means your app is using basically no CPU. You tell me if that's good...

I can't tell you what it's blocked by without a stack trace Rasp My guess given no information would be, presentRenderBuffer.
Quote this message in a reply
Member
Posts: 117
Joined: 2010.09
Post: #5
:-)
Well using no (or very little cpu time) sounds good too me.
So I guess my problem (framing out) is simply down to rendering and fill rate.

But yes, opening into that sema function does get down to presentrenderbuffer.

So I'm not cpu bound; just render bound :-/
Quote this message in a reply
Post Reply