Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
Announcements
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3058 Discussions

Why Media SDK h264 decoding needs so many virtual memory?

maoerwei
Beginner
‎03-13-2014 12:38 AM
248 Views

I tested Media SDK for h264 video decoding using HW accelerate, everything goes well but the virtual memory space occupying.

1 h264 video decoding (1280*720) took about 100MB virtual memory space in the test, and I monitored the memory index when decoding program was running, the committed memory is about 100MB, but the private working setting is only about 50MB, seems about half of the virtual memory is on the paging files.

I also tested the multi-channels h264 video decoding, the results was seem with the one-channel decoding, there is also about half of the virtual memory is on the paging files.

Is there any ways to decrease the decoding virtual memory space occupying? Because I need to process more than 16 channels of video coding in one process, it will use up to 2GB virtual memory address space.

0 Kudos

Link Copied

1 Reply
Anthony_P_Intel
Employee
‎03-18-2014 06:03 PM
248 Views

Hi,

You can save some memory by making sure to set ASyncDepth=1, but I believe you will still not have enough memory for 16 channels of 720p content.  We are constantly looking at ways to improve our memory footprint as well as performance, but we do not currently have a solution for supporting this usage in only 2GB.

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.