Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 115
    • Issues 115
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #702

Closed
Open
Created Dec 20, 2021 by Markus Scheidgen@mscheidgOwner

Exclude Calc from queuing (and slotting)

The Calc processing does not need any queuing (or slotting). Having to store additional keys, do additional updates, and most importantly add the additional risk of failure, should not be applied to 12M+ entries.

If we add queuing (and slotting) as additional features on top of Base it should happen in an other extending base class that is not used by Calc. I understand that @process does need to behave differently for those classes. But putting an "if" ?@process is less harmful than the alternative. The class can be determined from the self argument (or probably even from the function object).

Assignee
Assign to
Time tracking