Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gstreamer
gstreamer
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 403
    • Issues 403
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 78
    • Merge Requests 78
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #545

Closed
Open
Opened May 01, 2020 by Richard B. Kreckel@RBK💤Contributor

slooooowww binary registry cache writing

I'm running Linux and have an NFS-mounted homedir. Starting gstreamer applications is often terribly slow (ca. 2 min). This seems to be because priv_gst_registry_binary_write_chunk() is called about 17000 times, each time calling write(2). On NFS, this is very slow. (On the NFS server, the home directory is Btrfs-mounted and there it's blazingly fast.)

I haven't found out yet why the binary cache is re-written so often. Is this worth looking into? Alternatively, would building the binary registry cache in /tmp/ be an acceptable idea, and move it to its final destination in gst_registry_binary_cache_finish()?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gstreamer#545