Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
atilanevesoncode.wordpress.com
Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
1–10 of 50 posts
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#2"Since the Erlang unit tests are in the same files as the implementation, it’s hard to know exactly how many lines long it is. It gets worse since it implements most of MQTT, the D implementation essentially only implements what’s necessary to run the benchmarks."
Benchmarking the entire spec versus only the minimal set is almost certainly part of the problem here. If you want to benchmark implementations against each other, you should probably make sure they implement the same thing!
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#3> pingtest (latency - bigger is better)
This is an odd way to measure latency. Could someone explain further?
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#4Is there any hardware that uses MQTT?
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#5I'm the author but not the OP.
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#6"Since the Erlang unit tests are in the same files as the implementation, it’s hard to know exactly how many lines long it is. It gets worse since it implements most of MQTT, the D implementation essentially only implements what’s necessary to run the benchmarks." Benchmarking the entire spec versus only the minimal set is almost certainly part of the problem here. If you want to benchmark implementations against eac…
No, not really. I understand why you'd think that but knowing the MQTT spec and the benchmark, it shouldn't make any difference at all.
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#7I really can't imagine that this benchmark is relevant anymore. Haven't Go, D, and Erlang had major changes since then? E.g., Go is now compiled by a compiler written in Go.
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#8> pingtest (latency - bigger is better) This is an odd way to measure latency. Could someone explain further?
As someone pointed out to me later, it's not really latency but latency-constrained throughput.
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#9I really can't imagine that this benchmark is relevant anymore. Haven't Go, D, and Erlang had major changes since then? E.g., Go is now compiled by a compiler written in Go.
I'm planning on updating it this year once I finally find the time to learn Rust. Developing an MQTT broker has become my go-to task for learning new languages.
Re: Go, D, Erlang and C in real life: MQTT broker implementation shootout (2013)
#10update from go 1.2? since there have been many performance improvements since then...