I'm away from my Ultra 20 until after Christmas :-( I'll give this a go when I get back an post the results.
Brian Cameron wrote: > > Che: > > I just reran the test making sure that I had run gstreamer-properties > first > and set the "Default Output" plugin on the "Video" tab to "X Window > System > (X11/Xshm/Xv) so that Xvideo would be used. The upstream community > highlighted the ffmpegcolorspace plugin and the functions which seem to > be consuming the most CPU should only be used when using the non-Xvideo > sink. > > When running this way, the top 3 functions reported above do not > appear in > the report. This verifies that the liboil and ffmpegcolorspace functions > are not used when xvimagesink is used, and the overall performance is > much > better according to the Sun Studio collect/analyzer tool. > > Che, can you re-verify that setting your output plugin to xvideosink and > then running totem still has performance problems and stuttering on your > system? > > If you are still seeing high CPU usage and stuttering in the video when > using the Xvideo version of the video sink, then could you re-run the Sun > Studio "collect/analyzer" program to see if the above functions still > show > up in your report when using the Xvideo plugin? If you are seeing these, > then I am wondering if your system doesn't support Xvideo and somehow the > system is falling back to the non-Xvideo version. > > Brian > > >>> I ran a 172.541 second test, my top 3 were: >>> merge_linear_argb_ref (/usr/lib/liboil-0.3.so.0.3.0) with 56.039 >>> seconds >>> resample_linear_argb_ref (/usr/lib/liboil-0.3.so.0.3.0) with 39.708 >>> seconds >>> yuv420p_to_rgb32 (/usr/lib/gstreamer-0.10/libgstffmpegcolorspace.so) >>> with 19.324 seconds >>> >>> This seems to be in line with your suggestion that liboil and >>> libgstffmpegcolorspace were the offenders ...I will add this detail >>> to the bugs you have filed. >> >> Thanks. It's good to report these issues upstream, so hopefully the >> maintainers of the modules can address the problems. Also, since this >> issue seems to be affecting you, it might not be so hard to add some >> hardware acceleration yourself, then we could provide a patch to get >> upstream. If you have programming skills and an interest in learning >> about >> this, let me know offline and we can get you in touch with the right >> people >> at Sun who could help. >> >>> Many thanks for your guidance, I can categorically say that this >>> exercise has taught me something :) >> >> Great. I hope it taught you how easy it is to generate professional >> performance analysis reports on Solaris. On Solaris, this just works >> out of >> the box pretty easily as you notice, while on Linux using tools like >> valgrind an end-user probably would never be able to figure out how to >> generate a performance report like this. >> >> Brian >> > >
