Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-libav gst-libav
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-libavgst-libav
  • Merge requests
  • !72

avviddec: use a more conservative default number of threads

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Mathieu Duponchelle requested to merge meh/gst-libav:avviddec-conservative-max-threads into master May 21, 2020
  • Overview 12
  • Commits 1
  • Pipelines 2
  • Changes 1

When doing per-frame multithreading, FFmpeg introduces a delay of one frame per thread. On a machine with a high number of cores, the default maximum of 16 can easily lead to deadlocks in multiqueue.

The ideal situation would have multiqueue query a latency downstream to add to its maximum, but that's not easily implemented.

For now simply use a lower default maximum of 4, this should usually still be enough for real-time playback purposes, and can of course be set by the user through the max-threads property.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: avviddec-conservative-max-threads