-
Notifications
You must be signed in to change notification settings - Fork 26
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
Rabbitmq transport polling #175
Comments
adenhertog
added a commit
that referenced
this issue
Mar 12, 2022
* convert rabbit get to consume * lint fix
thanks for finding that @blankley . I've pushed a change that internally uses callbacks rather than loops that should be much easier on your CPU. This fix is available in the latest |
Thanks! Great fix. Not to sound ungrateful, but would it be possible to back port this to the 0.6.x tree? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're using rabbitmq as a transport and seeing very high cpu usage. We can see over 12k Gets a second and it looks like we're polling rabbit with no timeout :
I added a:
await new Promise(r => setTimeout(r,1000))
to
bus/packages/bus-rabbitmq/src/rabbitmq-transport.ts
Line 97 in f3843df
and see the expected 1 Get a second and normal CPU usage:
![Screenshot from 2022-03-11 13-07-35](https://user-images.githubusercontent.com/4763570/157973628-7050b486-3f3c-4a7d-bdf2-ddac9c5761cb.png)
Are we making a mistake in implementation? Missing something else?
The text was updated successfully, but these errors were encountered: