You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
I’m working on a NodeJS app, which reads messages from a Rabbit queue (a CF service). Based on a few rules, it dispatches each messages to one of a few output queues (also Rabbit).
The messages can come at a high speed (thousands per second), and the app can not process them quickly enough regardless of the number of instances. Our debugging shows that the CPU is hardly utilised and the network bandwith is the actual culprit.
We’re using DEA, and the team is not yet ready to migrate to Diego.
I read that Warden limits the bandwith of each CF app? If this is so, how can we increase the bandwith limit?
Thanks for your help in advance!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi folks,
I’m working on a NodeJS app, which reads messages from a Rabbit queue (a CF service). Based on a few rules, it dispatches each messages to one of a few output queues (also Rabbit).
The messages can come at a high speed (thousands per second), and the app can not process them quickly enough regardless of the number of instances. Our debugging shows that the CPU is hardly utilised and the network bandwith is the actual culprit.
We’re using DEA, and the team is not yet ready to migrate to Diego.
I read that Warden limits the bandwith of each CF app? If this is so, how can we increase the bandwith limit?
Thanks for your help in advance!
The text was updated successfully, but these errors were encountered: