D vs Go in real life, part 2. Also, Erlang.

[Dicebot]

On Wednesday, 4 December 2013 at 13:50:52 UTC, Atila Neves wrote:
> I'd have to dig in and see data to be convinced it's the GC 
> making the latency worse than the C implementation, but from 
> what I know you've got more experience with this so who knows :)

I am also not proficient enough with GC stuff to actually prove 
that but it fitted observations during my own tests pretty well. 
But I am not 100% sure.

> Doing this on a real network was waaay more work than I was 
> willing to put up with for something a colleague said during 
> lunch break, so it was done on localhost. The h/w is a Core i7 
> Lenovo laptop (W530) with 8GB of RAM running Arch Linux. My 
> server code can be found at https://github.com/atilaneves/mqtt, 
> the C implementation has its own website: http://mosquitto.org/.

Ah this is rather sad. It makes tests results somewhat unstable 
because client load interferes with server load. Ideally client 
should be separate machine and has more powerful h/w than server. 
However, that also requires ~gigabit network in between as well 
as matching network cards to hit the limits of top server 
performance - this makes such tests rather cumbersome to execute.

At the very least you should use process affinity to separate 
resources between client and server in more predictable manner.