Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Gauss Gauss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

GitLab Runners cleaning campaign ongoing (ETA 2nd October 2023). Check https://cern.ch/otg0078219 for further information.

  • LHCbLHCb
  • GaussGauss
  • Issues
  • #89
Closed
Open
Issue created Jan 12, 2023 by Michal Mazurek@mimazureDeveloper

Investigate multithreading options passed to LHCbApp and Gaussino

The following discussion from !912 (merged) should be addressed:

  • @mimazure started a discussion:

    These are multi-threading options that are set both for LHCbApp and Gaussino. Both of these configurables sets up the AvalancheSchedulerSvc. I think that we should not pass these options to LHCbApp and rely solely on Gaussino, but for some reason it does not work as expected. This needs more investigation.

Assignee
Assign to
Time tracking