-
Notifications
You must be signed in to change notification settings - Fork 6
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
Backend Stream taking up a lot of resources #64
Comments
Could be because of this setting - max.request.size: 3500042 Although this should not relate with the high CPU consumption shown above |
I restricted the CPU usage using docker-compose by adding the following parameter to streams service in docker-compose file (suggested by @afolarin ) - cpus: 2.0 This limits the CPU utilization of the container to 200%. That works fine for rosalind. Don't know how it affects the streams app though. I see a lot of rebalancing. Will wait and see if the streams start failing |
Good temporary fix. My hunch is that CPU usage is dominated by garbage collection, indeed because the streams take too much memory. Once the new sampling method in RADAR-Backend is deployed, memory requirements (11.6 GB according to htop!) and cpu usage should go down. |
We have a lot of memory on rosalind. Do you think if we increase the Min GC size then the CPU usage will go down? |
Increasing |
Just a question. Is this kind of behaviour normal for streams ?
Here is a screen grab of htop
The text was updated successfully, but these errors were encountered: