[rabbitmq-discuss] profiling

Mon Oct 7 09:28:20 BST 2013

You could also use erlang's built in tracing, though the timings wouldn't be highly accurate. Both approaches would require a pretty deep understanding of the code base to make sense of.

In most cases, it's better to measure things from an overall system standpoint, unless you're trying to benchmark internal changes to the broker.

So, what is it the OP is trying to do wih these numbers? Presumably there's some goal which the performance measurements and intended to help meet? What are we trying to achieve here? I don't remember having to benchmark tomcat or Postgres internals like that, when trying to make architectural decisions or plan SLAs around those technologies, some I'm curious why benchmarking rabbit at such a low level is desirable outside the development team. Not that we're opposed to folks doing this mind you - I'm quite happy to share some info about how to use erlang's tracing, dtrace/system-tap, etop and other tools of you're really keen on doing so. I just wonder why our MulticastMain performance measurememt tool isn't enough for your benchmarking requirements.

Cheers,
Tim

On 7 Oct 2013, at 08:39, Alvaro Videla <videlalvaro at gmail.com> wrote:

> Hi,
> 
> If you have a DTrace capable OS, you could compile Erlang with DTrace support and then profile every single detail from RabbitMQ. 
> 
> Not sure if that works in your case.
> 
> Regards,
> 
> Alvaro
> 
> 
> On Mon, Oct 7, 2013 at 2:31 AM, Suchak Jani <suchakjani at gmail.com> wrote:
> 
> Hi
> 
> Do we have any profiling inside rabbitmq server. 
> 
> I want to measure the time it takes for a message to be written to a clustered durable queue, across two nodes on different boxes in a network.
> 
> Within that time i would like to know
> 1) network time
> 2) disk io time
> 3) processing time
> 4) any other relevant time rabbit would take to process the message. 
> 
> -- 
> Regards
> 
> Suchak Jani
> 
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> 
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131007/67fb055b/attachment.htm>