[openstack-dev] [oslo.messaging]Optimize RPC performance by reusing callback queue

int32bit krystism at gmail.com
Thu Jun 8 02:29:16 UTC 2017


Currently, I find our RPC client always need create a new callback queue
for every call requests to track the reply belongs, at least in Newton.
That's pretty inefficient and lead to poor performance. I also  find some
RPC implementations no need to create a new queue, they track the request
and response by correlation id in message header(rabbitmq well supports,
not sure is it AMQP standard?). The rabbitmq official document provide a
simple demo, see [1].

So I am confused that why our oslo.messaging doesn't use this way
to optimize RPC performance. Is it for any consideration or do I miss
some potential cases?

Thanks for any reply and discussion!

[1] https://www.rabbitmq.com/tutorials/tutorial-six-python.html.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170608/384eb1dd/attachment.html>

More information about the OpenStack-dev mailing list