[rabbitmq-discuss] Optimizing RabbitMQ
Tim Watson
tim at rabbitmq.com
Fri Aug 17 16:43:50 BST 2012
Hi Tom
On 15 Aug 2012, at 14:59, Tom Wrigglesworth wrote:
> Hi, Thanks for your reply.
>
> So is the 40ms the time it takes for a message to travel from the game logic server to the web browser?
>
> It's the time between the message being published and the message being delivered. I have output from wireshark looking something similar to:
>
> # Time From To Protocol Length Info
> ...
> 155 1.539600 127.0.0.1 127.0.0.1 AMQP 115 Basic.Publish
> 157 1.579834 127.0.0.1 127.0.0.1 AMQP 3873 Content-Header Content-Body
> 159 1.580942 127.0.0.1 127.0.0.1 AMQP 3963 Basic-Deliver Content-Header Content-Body
> 160 1.590769 127.0.0.1 127.0.0.1 AMQP 115 Basic.Publish
> 162 1.627732 127.0.0.1 127.0.0.1 AMQP 3873 Content-Header Content-Body
> 164 1.628295 127.0.0.1 127.0.0.1 AMQP 3963 Basic-Deliver Content-Header Content-Body
> 165 1.638748 127.0.0.1 127.0.0.1 AMQP 115 Basic.Publish
> 167 1.675834 127.0.0.1 127.0.0.1 AMQP 3873 Content-Header Content-Body
> 169 1.676850 127.0.0.1 127.0.0.1 AMQP 3963 Basic-Deliver Content-Header Content-Body
> ...
>
> This looks to me like it is AMQP that is taking about 40ms between publish and deliver. Is this because of certain server settings i'm running, interference from the node server running at the same time on the same machine or some other reason?
The only way I can think of to determine that is to remove the other factors. You could try publishing and consuming via the same client instance, with the other servers disabled and see what kind of throughput you get when there's little other potential contention for operating system resources.
Cheers,
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120817/888d6288/attachment.htm>
More information about the rabbitmq-discuss
mailing list