Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Project Juggler Project Juggler
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • EIC
  • Project JugglerProject Juggler
  • Issues
  • #77

Closed
Open
Created Jan 15, 2022 by Wouter Deconinck@wdconincOwner

Source linker storage performance

As pointed out by Paul Gessinger, https://github.com/acts-project/acts/issues/1106#issuecomment-989624406:

One thing I noticed when looking at the MR over on your Gitlab is that you copied the pattern from our fitting algorithm, where I introduced an std::list to have stable pointers for the source links I create. This is not necessarily a good idea for a setup meant for any kind of production: std::list is relatively slow. I didn't add anything more clever to that algorithm there because it wasn't needed, but I would suggest you try to work around using this pattern, for example by creating the source links in one pass and only afterwards creating the measurements (when source link pointers are stable)

This needs some thinking.

Assignee
Assign to
Time tracking