Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-rs gst-plugins-rs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 28
    • Merge requests 28
  • 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-plugins-rsgst-plugins-rs
  • Issues
  • #107
Closed
Open
Issue created Apr 08, 2020 by François Laignel@fengalinDeveloper

threadshare: use bench to select appropriate Mutexes

Depending on the contention model and sync / async usage, several locking mechanisms are available:

  • std::sync::Mutex.
  • std::sync::RwLock.
  • futures::lock::Mutex.
  • parking_lot:*
  • simple-mutex.

We should use benches to select the most efficient candidate.

Note that smol might be used as a basis for the executor and can lead to different results.

See !298 (comment 458654) and !282 (comment 448814).

Edited May 26, 2020 by François Laignel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking