Showing results for 
Search instead for 
Did you mean: 

Decoder performance in i5


Can you please provide some figure where with an system with the following configuration how many simultaneous decoding of 1920*1080@25fps is possible?


The following versions of Media SDK API are supported by platform/driver:

        Version Target  Supported       Dec     Enc
        1.0     HW      Yes             X       X
        1.0     SW      Yes             X       X
        1.1     HW      Yes             X       X
        1.1     SW      Yes             X       X
        1.3     HW      Yes             X       X
        1.3     SW      Yes             X       X
        1.4     HW      Yes             X       X
        1.4     SW      Yes             X       X
        1.5     HW      Yes             X       X
        1.5     SW      Yes             X       X
        1.6     HW      Yes             X       X
        1.6     SW      Yes             X       X
        1.7     HW      Yes             X       X
        1.7     SW      Yes             X       X
        1.8     HW      Yes             X       X
        1.8     SW      Yes             X       X

Graphics Devices:
        Name                                         Version             State
        Intel(R) HD Graphics Family               Active
        NVIDIA GeForce 840M                       08

System info:
        CPU:    Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
        OS:     Microsoft Windows 10 Home Single Language
        Arch:   64-bit




0 Kudos
1 Reply

The best way to check hardware peak decode performance is to do a quick experiment, like this:

sample_decode.exe h264 -i test_1920x1080.h264 -hw -d3d

On my i5-4570 (with a more recent driver) I'm seeing this with "Tears of Steel" resized to 1920x1080 as an input:

17616 frames / 20.8 seconds = 846.9 FPS

So, looking at decode alone, this could support up to 33 decodes at 25 FPS.  However, with such fast decode other things (usually considered tiny) become the main bottlenecks.  For example, if your pipeline involves moving the raw frame data back to the CPU the total number of decodes you can support will be significantly lower.  Or if your goal is to render you will need to resize to show this number of streams on the screen and resize is likely to become the main bottleneck.  In general, decode is fast enough that the bottleneck is usually something else.

Regards, Jeff