Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: The worker component takes up too much memory on multi-core CPUs #6671

Open
1 task done
TheresaQWQ opened this issue Feb 25, 2025 · 0 comments
Open
1 task done
Assignees
Labels
🐛bug Something isn't working ⚡performance

Comments

@TheresaQWQ
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Using a server with enough cores (e.g. 32 cores), start Plane using docker or Kubernetes, and observe the logs to see celery Killed, etc. This is due to the fact that celery uses the number of CPU cores as the number of threads by default, which leads to the memory usage exceeding the default memory limits

I hope it's possible to limit the number of threads by adding, for example, a parameter like "--concurrency=8".

Steps to reproduce

Using a server with enough cores (e.g. 32 cores), start Plane using docker or Kubernetes, then, boom!

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.8.1 (helm)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working ⚡performance
Projects
None yet
Development

No branches or pull requests

6 participants