VDPAU testing tool - Page 13

Lysius · 08-06-09, 11:17 AM

I'm using 190.18 with my 8800GTS 512 (G92) on Fedora11 x86_64.
I have tried using plain X without anything running (just xterm), does not make any difference.
I changed GPU and Memory Clock settings with nvidia-settings. That seems to work, at least glxgears performance is lowered when I reduce the clock speeds.

GPU@650/972 (GPU Clock/Memory Clock)

Code:

Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
26:20 NVIDIA(0): NVIDIA GPU GeForce 8800 GTS 512 (G92) at PCI:1:0:0 (GPU-0)

VDPAU API version : 0
VDPAU implementation : NVIDIA VDPAU Driver Shared Library  190.18  Wed Jul 22 16:37:05 PDT 2009

SURFACE GET BITS: 991.745 M/s
SURFACE PUT BITS: 1077.09 M/s

MPEG DECODING (1920x1080): 79 frames/s
MPEG DECODING (1280x720): 157 frames/s
H264 DECODING (1920x1080): 45 frames/s
H264 DECODING (1280x720): 99 frames/s
VC1 DECODING (1440x1080): 123 frames/s

MIXER WEAVE (1920x1080): 2409 frames/s
MIXER BOB (1920x1080): 4362 fields/s
MIXER TEMPORAL (1920x1080): 946 fields/s
MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 1250 fields/s
MIXER TEMPORAL_SPATIAL (1920x1080): 405 fields/s
MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 452 fields/s

MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 1404 fields/s

SURFACE GET/SET BITS seems to be mainly affected by the CPU (100% usage, scales quite linear with CPU frequency), but only very little by the GPU Clock (GET goes down to 885 M/s with GPU@162/430).

MIXER scales nearly linear with GPU frequency/Memory frequency, but is almost independent of the CPU Clock.

Decoding shows only a very slight dependence of the GPU/Memory Clock
GPU@162/430 (GPU Clock/Memory Clock)

Code:

MPEG DECODING (1920x1080): 74 frames/s
MPEG DECODING (1280x720): 144 frames/s
H264 DECODING (1920x1080): 37 frames/s
H264 DECODING (1280x720): 79 frames/s
VC1 DECODING (1440x1080): 111 frames/s

CPU-usage is about 30% in the tests and performance does barely change if I throttle down the CPU just a little (throttle to 75%, 2GHz)

Code:

MPEG DECODING (1920x1080): 75 frames/s
MPEG DECODING (1280x720): 156 frames/s
H264 DECODING (1920x1080): 45 frames/s
H264 DECODING (1280x720): 99 frames/s
VC1 DECODING (1440x1080): 115 frames/s

If I throttle the CPU to 10%, and limit CPU-Clock to 2GHz, I get

Code:

MPEG DECODING (1920x1080): 15 frames/s
MPEG DECODING (1280x720): 50 frames/s
H264 DECODING (1920x1080): 45 frames/s
H264 DECODING (1280x720): 96 frames/s
VC1 DECODING (1440x1080): 14 frames/s

MPEG and VC1 is mainly dependent on CPU, but when CPU works at full power, this is not the main limiting factor.
So H264 is independent of CPU and only slightly depends on GPU Clock, where is the limiting factor here?

And some feedback on the test:
- Would be nice if the programm exits when I press "esc". I's useful mainly when running in plain X without window manager.
- There need to be command line options to run only single tests
- The rates for get/put have too many digits that are not statistically significant. I think all post decimal positions can be left out without loss in precision.

raptorjr · 09-03-09, 12:49 PM

I've compared my numbers with others in this thread and something feels really wrong with my system. Should my card really be this slow? I cant play any 1080p file with mplayer without getting YOUR SYSTEM IS TOO SLOW.

Code:

Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
NVIDIA GPU GeForce 9400 GT (G96) at PCI:1:0:0 (GPU-0)

VDPAU API version : 0
VDPAU implementation : NVIDIA VDPAU Driver Shared Library  185.18.36  Fri Aug 14 17:50:51 PDT 2009

SURFACE GET BITS: 265.584 M/s
SURFACE PUT BITS: 169.491 M/s

MPEG DECODING (1920x1080): 64 frames/s
MPEG DECODING (1280x720): 133 frames/s
H264 DECODING (1920x1080): 25 frames/s
H264 DECODING (1280x720): 51 frames/s
VC1 DECODING (1440x1080): 90 frames/s

MIXER WEAVE (1920x1080): 154 frames/s
MIXER BOB (1920x1080): 259 fields/s
MIXER TEMPORAL (1920x1080): 63 fields/s
MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 90 fields/s
MIXER TEMPORAL_SPATIAL (1920x1080): 36 fields/s
MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 43 fields/s

MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 103 fields/s

Is there any settings i could change to get this working?

cehoyos · 09-03-09, 05:03 PM

Quote:

Originally Posted by raptorjr

Code:

H264 DECODING (1920x1080): 25 frames/s

Looking at my posting (#47 in this thread), yes, this is a very low number and explains why you have playback problems.

Carl Eugen

raptorjr · 09-04-09, 04:11 AM

If i understand everything right a 9400GT should be able to show 1080p? Worst case i need to go back to CoreAVC.
I've tried to read the whole thread and i cant find much help on what i could try to find the problem with my system. Is there anyone with some more knowledge that could give me some help on what to try and look for to find the problem?

cehoyos · 09-04-09, 04:55 AM

Quote:

Originally Posted by raptorjr

Is there anyone with some more knowledge that could give me some help on what to try and look for to find the problem?

You could open a new thread with a bug-report as explained in the sticky.

Carl Eugen

raptorjr · 09-04-09, 06:07 AM

Quote:

Originally Posted by cehoyos

You could open a new thread with a bug-report as explained in the sticky.

Carl Eugen

Yes, i could do that. Was just thinking that there were things to try before it was considered a bug. But i will look at the sticky.
But before i do that i could need some confirmation that a 9400GT should be able to play a 1080p file? Otherwise i will just have to accept how it is.

crisalide · 09-04-09, 08:07 AM

All VDPAU capable cards can play 1080.
Looking at your test results, the following is strange given your cpu:

SURFACE GET BITS: 265.584 M/s
SURFACE PUT BITS: 169.491 M/s

Something wrong with your ram bios settings?

raptorjr · 09-04-09, 08:40 AM

Quote:

Originally Posted by crisalide

All VDPAU capable cards can play 1080.
Looking at your test results, the following is strange given your cpu:

SURFACE GET BITS: 265.584 M/s
SURFACE PUT BITS: 169.491 M/s

Something wrong with your ram bios settings?

I think i remember some setting in bios about the ram. It has 3 modes, standard, turbo, extreme. It was default at turbo and i didn't change it because i'm not sure on what it would do. Maybe i should try some other setting?

raptorjr · 09-04-09, 11:25 AM

So, i found the setting again in bios about DRAM, changed to extreme to get the most performance from the memory. Got these numbers:

Code:

Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
NVIDIA GPU GeForce 9400 GT (G96) at PCI:1:0:0 (GPU-0)

VDPAU API version : 0
VDPAU implementation : NVIDIA VDPAU Driver Shared Library  185.18.36  Fri Aug 14 17:50:51 PDT 2009

SURFACE GET BITS: 1026.76 M/s
SURFACE PUT BITS: 658.631 M/s

MPEG DECODING (1920x1080): 75 frames/s
MPEG DECODING (1280x720): 153 frames/s
H264 DECODING (1920x1080): 44 frames/s
H264 DECODING (1280x720): 93 frames/s
VC1 DECODING (1440x1080): 118 frames/s

MIXER WEAVE (1920x1080): 229 frames/s
MIXER BOB (1920x1080): 388 fields/s
MIXER TEMPORAL (1920x1080): 103 fields/s
MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 137 fields/s
MIXER TEMPORAL_SPATIAL (1920x1080): 57 fields/s
MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 65 fields/s

MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 191 fields/s

Great, much better i thought. Started mplayer to watch a file. YOUR SYSTEM IS TOO SLOW!!! What!?!?

Checked with qvdpautest again and got this:

Code:

Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
NVIDIA GPU GeForce 9400 GT (G96) at PCI:1:0:0 (GPU-0)

VDPAU API version : 0
VDPAU implementation : NVIDIA VDPAU Driver Shared Library  185.18.36  Fri Aug 14 17:50:51 PDT 2009

SURFACE GET BITS: 264.979 M/s
SURFACE PUT BITS: 170.162 M/s

MPEG DECODING (1920x1080): 64 frames/s
MPEG DECODING (1280x720): 132 frames/s
H264 DECODING (1920x1080): 25 frames/s
H264 DECODING (1280x720): 51 frames/s
VC1 DECODING (1440x1080): 90 frames/s

MIXER WEAVE (1920x1080): 153 frames/s
MIXER BOB (1920x1080): 258 fields/s
MIXER TEMPORAL (1920x1080): 64 fields/s
MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 90 fields/s
MIXER TEMPORAL_SPATIAL (1920x1080): 36 fields/s
MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 43 fields/s

MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 102 fields/s

Is it only after a restart i get good numbers? Restarted again, but still, the same bad numbers. Dont know what happened when it was good. So something is going on, but i dont know what? Bad hardware or bad software? Haven't got any other problems with the hardware, only VDPAU that is messing with me.

Lost Dog · 09-04-09, 01:07 PM

Quote:

Originally Posted by raptorjr

Is it only after a restart i get good numbers? Restarted again, but still, the same bad numbers. Dont know what happened when it was good. So something is going on, but i dont know what? Bad hardware or bad software? Haven't got any other problems with the hardware, only VDPAU that is messing with me.

Not sure if you posted it anywhere but are you sure you are using the correct mplayer commands to play using VDPAU? Have you tried Xine-vdpau?

raptorjr · 09-04-09, 01:49 PM

Well i do get this from mplayer:

Code:

Matroska file format detected.
VIDEO:  [avc1]  1920x1080  24bpp  23.976 fps    0.0 kbps ( 0.0 kbyte/s)
==========================================================================
Forced video codec: ffh264vdpau
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
[VD_FFMPEG] XVMC-accelerated MPEG-2.
Selected video codec: [ffh264vdpau] vfm: ffmpeg (FFmpeg H.264 (VDPAU))
==========================================================================
==========================================================================
Opening audio decoder: [liba52] AC3 decoding with liba52
Using SSE optimized IMDCT transform
Using MMX optimized resampler
AUDIO: 48000 Hz, 2 ch, s16le, 448.0 kbit/29.17% (ratio: 56000->192000)
Selected audio codec: [a52] afm: liba52 (AC3-liba52)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
[VD_FFMPEG] XVMC-accelerated MPEG-2.
VDec: vo config request - 1920 x 1080 (preferred colorspace: H.264 VDPAU acceleration)
VDec: using H.264 VDPAU acceleration as output csp (no 0)
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [vdpau] 1920x1080 => 1920x1080 H.264 VDPAU acceleration  [fs]

I guess it looks right for VDPAU?

I'm getting more and more confused. Now, without changing anything i've been able to play several files without a problem. And running qvdpautest several times also with good numbers. What is happening? VDPAU is very unstable for me. Seem to work sometimes.

I would be happy to submit a bug report, but does this behavior suggest that it is a driver issue?

**Stephen Warren** · 09-04-09, 04:23 PM

raptorjr, Double-check any CPU-/bus-throttling settings. Perhaps bad performance correlates with a throttled CPU? Also, open nvidia-settings to the PowerMizer page and make sure it isn't stuck at the lowest setting when playing video.

08-06-09, 11:17 AM	#145
Lysius Registered User Join Date: Oct 2008 Posts: 98	Re: VDPAU testing tool I'm using 190.18 with my 8800GTS 512 (G92) on Fedora11 x86_64. I have tried using plain X without anything running (just xterm), does not make any difference. I changed GPU and Memory Clock settings with nvidia-settings. That seems to work, at least glxgears performance is lowered when I reduce the clock speeds. GPU@650/972 (GPU Clock/Memory Clock) Code: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz 26:20 NVIDIA(0): NVIDIA GPU GeForce 8800 GTS 512 (G92) at PCI:1:0:0 (GPU-0) VDPAU API version : 0 VDPAU implementation : NVIDIA VDPAU Driver Shared Library 190.18 Wed Jul 22 16:37:05 PDT 2009 SURFACE GET BITS: 991.745 M/s SURFACE PUT BITS: 1077.09 M/s MPEG DECODING (1920x1080): 79 frames/s MPEG DECODING (1280x720): 157 frames/s H264 DECODING (1920x1080): 45 frames/s H264 DECODING (1280x720): 99 frames/s VC1 DECODING (1440x1080): 123 frames/s MIXER WEAVE (1920x1080): 2409 frames/s MIXER BOB (1920x1080): 4362 fields/s MIXER TEMPORAL (1920x1080): 946 fields/s MIXER TEMPORAL + SKIP_CHROMA (1920x1080): 1250 fields/s MIXER TEMPORAL_SPATIAL (1920x1080): 405 fields/s MIXER TEMPORAL_SPATIAL + SKIP_CHROMA (1920x1080): 452 fields/s MIXER TEMPORAL_SPATIAL (720x576 video to 1920x1080 display): 1404 fields/s SURFACE GET/SET BITS seems to be mainly affected by the CPU (100% usage, scales quite linear with CPU frequency), but only very little by the GPU Clock (GET goes down to 885 M/s with GPU@162/430). MIXER scales nearly linear with GPU frequency/Memory frequency, but is almost independent of the CPU Clock. Decoding shows only a very slight dependence of the GPU/Memory Clock GPU@162/430 (GPU Clock/Memory Clock) Code: MPEG DECODING (1920x1080): 74 frames/s MPEG DECODING (1280x720): 144 frames/s H264 DECODING (1920x1080): 37 frames/s H264 DECODING (1280x720): 79 frames/s VC1 DECODING (1440x1080): 111 frames/s CPU-usage is about 30% in the tests and performance does barely change if I throttle down the CPU just a little (throttle to 75%, 2GHz) Code: MPEG DECODING (1920x1080): 75 frames/s MPEG DECODING (1280x720): 156 frames/s H264 DECODING (1920x1080): 45 frames/s H264 DECODING (1280x720): 99 frames/s VC1 DECODING (1440x1080): 115 frames/s If I throttle the CPU to 10%, and limit CPU-Clock to 2GHz, I get Code: MPEG DECODING (1920x1080): 15 frames/s MPEG DECODING (1280x720): 50 frames/s H264 DECODING (1920x1080): 45 frames/s H264 DECODING (1280x720): 96 frames/s VC1 DECODING (1440x1080): 14 frames/s MPEG and VC1 is mainly dependent on CPU, but when CPU works at full power, this is not the main limiting factor. So H264 is independent of CPU and only slightly depends on GPU Clock, where is the limiting factor here? And some feedback on the test: - Would be nice if the programm exits when I press "esc". I's useful mainly when running in plain X without window manager. - There need to be command line options to run only single tests - The rates for get/put have too many digits that are not statistically significant. I think all post decimal positions can be left out without loss in precision.

09-04-09, 04:11 AM	#148
raptorjr Registered User Join Date: Sep 2009 Posts: 8	Re: VDPAU testing tool If i understand everything right a 9400GT should be able to show 1080p? Worst case i need to go back to CoreAVC. I've tried to read the whole thread and i cant find much help on what i could try to find the problem with my system. Is there anyone with some more knowledge that could give me some help on what to try and look for to find the problem?

09-04-09, 08:07 AM	#151
crisalide Registered User Join Date: Dec 2008 Posts: 173	Re: VDPAU testing tool All VDPAU capable cards can play 1080. Looking at your test results, the following is strange given your cpu: SURFACE GET BITS: 265.584 M/s SURFACE PUT BITS: 169.491 M/s Something wrong with your ram bios settings?

09-04-09, 04:23 PM	#156
Stephen Warren Moderator Join Date: Aug 2005 Posts: 1,327	Re: VDPAU testing tool raptorjr, Double-check any CPU-/bus-throttling settings. Perhaps bad performance correlates with a throttled CPU? Also, open nvidia-settings to the PowerMizer page and make sure it isn't stuck at the lowest setting when playing video.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Valve to release its trailer-making tool: Source Filmmaker	dikinher	Gaming Central	2	06-28-12 12:28 PM
xorg locks-up with newest nvidia drivers w/ vdpau.	theroot	NVIDIA Linux	1	06-24-12 11:04 AM
Load Testing with the Cloud ' This Week on inside* Publications	News	Latest Tech And Game Headlines	0	05-20-12 05:30 PM
Portal 2 Perpetual Testing Initiative Starts Now	News	Latest Tech And Game Headlines	0	05-08-12 05:00 PM
tv tool 6.8	thcdru2k	NVIDIA Windows Graphics Drivers	4	10-18-02 01:10 PM