Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Issues
  • #2543
Closed
Open
Issue created Feb 07, 2023 by ElFisherMan@ElFisherMan

[Question] Repeatable jobs with several nodejs instances - performance

I understand that when using Repeatable Jobs with several nodejs instances (same queue name, same jobId and cron string for the job), the job gets executed once across all instances per time "slot".

Regrading the perf:

  1. Only one instance will spend CPU on every execution? or maybe every one of the instances will wake up?
  2. Will it use the main thread (AKA the event loop)?
  3. When using separate process - 3.1. Will it handle the repeated job? 3.2. In case every instances wakes up, will it happen in the different process or the event loop?

Thanks!

Assignee
Assign to
Time tracking