I see the question is being handled by one of the colleagues, can you please reply to his answer, copying here again(in case you didn't see) -
Hi Ramashankar,
One approach you can try is to model your pipeline with the Media SDK sample applications.
If your final goal is transcode it may make sense to start with sample_multi_transcode instead of looking at decode, VPP, and encode separately since we have multiple hardware blocks that can run concurrently.
If you want to just look at decode+vpp you can start with sample_decvpp
sample_decvpp h264 -rgb4 -d3d -async 4 -hw -i test_sequence.h264
Or you could just look at decode itself:
sample_decode h264 -hw -d3d -async 4 -i test_sequence.h264
These two command lines don't include an output so you can separate hardware performance from disk I/O. If there is a big difference between sample performance and your code then you can start looking at what your application is doing. On the other hand, if you see the same behavior with the samples then it is more likely to be a configuration issue.
Do you see the same behavior ratios running the samples without outputs?
