[Bug 759742] nvenc: very high CPU load when multiple nvenc instances are initialised at the same time

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=759742

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.7.1
            Summary|Running multiple nvenc      |nvenc: very high CPU load
                   |encoders in the same        |when multiple nvenc
                   |pipeline causes very high   |instances are initialised
                   |CPU load during             |at the same time
                   |initialisation              |

--- Comment #5 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Thanks, I've moved the comment about the lock up to where it's defined, but
otherwise pushed as-is.

ommit 0e34c02dd60f8d301a1b4c1bbcd3c90ee05bdb0a
Author: Matthew Marsh <matt at stonethree.com>
Date:   Tue Dec 22 11:10:31 2015 +0200

    nvenc: fix high CPU use on initialization of multiple encoders at the same
time

    We need a static lock to protect various NVENC methods in _set_format().
Without
    this the CPU use increases dramatically on initialisation of the element
when
    there are multiple elements being initialised at the same time.

    https://bugzilla.gnome.org/show_bug.cgi?id=759742

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.