On Feb 2, 2010, at 12:57 PM, Alex Harrington wrote:

>
>> Maybe the machine is busy waiting? What happens if you set framerate
>> to 1000?
>
> Incidently setting the framerate to 60 on this machine does achieve  
> some improvement. CPU sits aroun 120% with the following profile:
>
> [10-02-02 12:04:20.435] PROFILE: Profile Statistics (in us):
> [10-02-02 12:04:20.435] PROFILE: Thread main
> [10-02-02 12:04:20.435] PROFILE: Zone name                           
> Avg. time
> [10-02-02 12:04:20.435] PROFILE: ---------                           
> ---------
> [10-02-02 12:04:20.435] PROFILE: Player - Total frame  
> time              19047
> [10-02-02 12:04:20.435] PROFILE:   Player -  
> handleTimers                    0
> [10-02-02 12:04:20.435] PROFILE:   Player - dispatch  
> events                17
> [10-02-02 12:04:20.435] PROFILE:   Player -  
> PreRender                       0
> [10-02-02 12:04:20.435] PROFILE:   Player -  
> render                      19022
> [10-02-02 12:04:20.435] PROFILE:     Root node:  
> render                   3124
> [10-02-02 12:04:20.435] PROFILE:        
> pushClipRect                      1162
> [10-02-02 12:04:20.435] PROFILE:        
> Words::render                      663
> [10-02-02 12:04:20.435] PROFILE:        
> popClipRect                       1116
> [10-02-02 12:04:20.435] PROFILE:     Render -  
> wait                      10718
> [10-02-02 12:04:20.435] PROFILE:     Render - swap  
> buffers               2705
> [10-02-02 12:04:20.435] PROFILE:   Player -  
> onFrameEnd                      0
> [10-02-02 12:04:20.435] PROFILE:
> [10-02-02 12:04:20.435] PROFILE: Framerate statistics:
> [10-02-02 12:04:20.435] PROFILE:   Total frames: 1292
> [10-02-02 12:04:20.435] PROFILE:   Total time: 25.1078 seconds
> [10-02-02 12:04:20.435] PROFILE:   Framerate achieved: 51.498
> [10-02-02 12:04:20.435] PROFILE:   Frames too late: 277
> [10-02-02 12:04:20.435] PROFILE:   Percent of time spent waiting:  
> 71.8715
> [10-02-02 12:04:20.435] PROFILE:   Framerate goal was: 60

The strange thing here is that libavg reports that the program is  
waiting (in other words: doing nothing) most of the time, which more  
or less maps to a usleep() call. It's really hard to debug this from  
afar, but to me this looks like a configuration problem.

> Still no clean exit though on escape.


I can have a look at what's happening there if you start the program  
in gdb, hit ctrl-C when it hangs and send me a stack trace.

make check exits cleanly? Strange.

Cheers,

   Uli

--
Any technology distinguishable from magic is insufficiently advanced.

Ulrich von Zadow | +49-172-7872715
Jabber: [email protected]
Skype: uzadow




_______________________________________________
libavg-users mailing list
[email protected]
https://mail.datenhain.de/mailman/listinfo/libavg-users

Reply via email to