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
  • #1361
Closed
Open
Issue created Jun 24, 2019 by Administrator@rootContributor

Redis size assessment

Created by: orgalaf

Hi, Not really a bug rather a request for better docs. Recently tried deploying bull in production over aws elasticache to replace rabbitmq. We estimated the data size to be about 20GB and provisioned a 30GB redis instance. After about 15 mins in production we had about 10GB of data in redis and started getting OOM errors. A bit of research revealed that write heavy applications over redis (as bulljs is) can incur significant memory overhead up to twice the size of the actual data.

Would be good to get some guidelines in the docs about what size of instance to provision for the expected load.

Thanks

Assignee
Assign to
Time tracking