Skip to content

High cpu usage when using openh264 built by meson in GStreamer. #3876

Open
@pwjworks

Description

@pwjworks

My application is using GStreamer 1.24.8 MSVC official build on Windows 10 x86_64 which is built by meson. I found that when encoding camera data using openh264 in GStreamer, cpu usage is significantly higher than that using cisco official build.

This seems to be caused by not having the avx command turned on in meson.build.

I tried the solution below and could see significant drop in cpu usage. I wonder if this probably be added as a build option and add runtime detection in meson.build.

... cpu_family == 'x86_64'
    asm_format = 'win64'
    asm_args += ['-DWIN64', '-DX86_ASM','-DHAVE_AVX2']
    add_project_arguments('-DHAVE_AVX2', '-DX86_ASM', language: 'cpp')
    add_project_arguments('-DHAVE_AVX2', '-DX86_ASM', language: 'c')
    asm_inc = join_paths(meson.current_source_dir(), 'codec', 'common', 'x86', '')

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions