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
  • #1008
Closed
Open
Issue created Jul 24, 2018 by Administrator@rootContributor

A lot of separate processes and memory consumption

Created by: Kupuyc

Hi.

I have about 18 queues at this moment and each runs with concurrency 5-10. So, there are about 160 child processes in memory and 16GB is not enough. Is it possible to kill them time by time (for example when queue is idle for some time)?

I tried to use Queue:childPool:clean() and Queue:close() but these methods destructs queue and I must to call all chain of methods to recreate queue from scratch and set process function. Something like this:

const a = new Queue();
a.process(...);

Without such code, jobs are created, but not processed.

Assignee
Assign to
Time tracking