Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BornAgain BornAgain
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 190
    • Issues 190
    • 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
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mlzmlz
  • BornAgainBornAgain
  • Merge requests
  • !8

Remove quadratic scaling with number of layers

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Beerwerth, Randolf requested to merge performance-parameters into develop Mar 12, 2021
  • Overview 0
  • Commits 2
  • Pipelines 1
  • Changes 2

This PR removes the quadratic scaling with the number of layers:

  • when creating a multilayer
  • when running a simulation, as long as no parameter distribution is present

As a result, the runtime is pretty linear now also for large numbers of layers. "Old" in these plots refers to timings before MR !7 (merged). compare_np_const

For completeness, updated timing with constant number of layers. Again, compared to the state before MR !7 (merged). compare_nl_const

More timing results: Here, it is split into the full runtime (create sample + create simulation + run simulation) and only the run step (run simulation). For constant number of layers: compare_nl_const_run For constant number of Q points compare_np_const_run

All timings were done with a single thread and without any resolution correction. Multi-threading slows things down considerably for small numbers of layers and points.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: performance-parameters