[erlang-questions] Re: 20k messages in 4s but want to go faster!

[Dave Smith]

Given that your average is so close to your max, I would hazard a
guess that you would benefit from analyzing the latency distribution
by percentile. The statistical mean is a handy tool, but for latency
problems I've found it can often be very misleading.

D.

On Mon, Jul 13, 2009 at 12:15 PM, Joel Reymont<joelr1@REDACTED> wrote:
> I changed my timing approach but it didn't seem to affect results much.
>
> setup time: 4412.022ms, n: 10000, run time: 6589.50ms
> min: 18.13ms, avg: 2074.14ms, max: 2074.22ms
>
> setup time: 7310.474ms, n: 10000, run time: 9444.31ms
> min: 0.39ms, avg: 2079.99ms, max: 2080.07ms
>
> setup time: 36879.026ms, n: 10000, run time: 39055.65ms
> min: 0.39ms, avg: 2117.59ms, max: 2117.66ms
>
> This is a 10k bot run on my MacBook Pro, 2 nodes, unicasting to the socket
> via a session process and then the transport process.
>
> Sending directly to the socket is not much different.
>
> I calculate setup time from when the run has started and until all bots
> checked in as ready.
>
> Minimum latency is really surprising here and it's something that I'm going
> to focus on.
>
>        Thanks, Joel
>
> ---
> Mac hacker with a performance bent
> http://www.linkedin.com/in/joelreymont
>
>
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
>
>