[nanomsg] Re: benchmarks
- From: Garrett D'Amore <garrett@xxxxxxxxxx>
- To: "nanomsg@xxxxxxxxxxxxx" <nanomsg@xxxxxxxxxxxxx>
- Date: Sat, 14 Feb 2015 07:56:37 -0800
Btw the hardware in that case was a 2014 iMac and op is a full req/rep
exchange. I.e. I start the clock on transmit of the req and stop it on recv of
the reply.
And even my latest post back in April is old. We get better numbers now and
mangos has new options to help tune the dial between throughput and latency.
And newer Go versions have helped as well.
I also now understand the dips around IPC. Basically perf sucks there because
the MTU is usually a small 576 bytes or somesuch. Leading to multiple system
calls. Using it therefore is suboptimal for the cases where you have larger
payloads.
I believe Tyler Treat also has done some benchmarking here as well. You can
see more about that here : http://www.bravenewgeek.com/benchmark-responsibly/
Sent from my iPhone
> On Feb 14, 2015, at 2:33 AM, Drew Crawford <drew@xxxxxxxxxxxxxxxxxx> wrote:
>
> Are there any benchmarks published for nanomsg / mangos?
>
> As is sort of an open secret I’m working on a new speed-focused
> implementation of some of the SP protocols. I got the tests passing on the
> first few pieces of my architecture today and measured some initial timings.
> However I don’t really have a standard of comparison to know “am I fast yet”
> and by how much.
>
> I did dig up http://itnewscast.com/servers-storage/early-performance-numbers
> but that is old and leaves out some key details (like what is an “op” and
> what kind of hardware was used).
>
> However if those are the current order-of-magnitude timings for req/rep on
> modern Intel hardware then let’s just say I’m a happy camper...
Other related posts:
