Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • castellum castellum
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CastellumCastellum
  • castellumcastellum
  • Merge requests
  • !2090

avoid session-scoped fixtures

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Bengfort requested to merge rm-session-scoped-fixtures into main Oct 20, 2021
  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

In !2089 (merged) I had some issues with session-scoped fixtures. So I wanted to check how much of a performance gain we get from them and if it is worth the additional complexity.

I started with groups and study_groups because they were relatively easy to do. The result (averaged over 10 runs):

  • session-scoped: 32.793 s
  • not session-scoped: 38.470 s

So the not-session-scoped version takes 17 % longer. IMHO that is enough to justify the complexity.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: rm-session-scoped-fixtures