4 ms·
> Go 1.2 produces a binary that performs on the order of 10%-15% faster than the numbers above, which might mean equivalent performance to the Erlang implementa
by rdtsc 13y ago
> Go 1.2 produces a binary that performs on the order of 10%-15% faster than the numbers above, which might mean equivalent performance to the Erlang implementation.
Huh, impressive for Erlang, beating a newer, statically compiled language, while being interpreted and with dynamic types.
- pgeorgi 13y agonewer, statically compiled language with a minimalist, unoptimized compiler versus an interpreter that got decades to mature (and HiPE to speed things up some more)
- pvalsecc 13y agoI didn't use HIPE. It was providing no performance improvement for this use case.
- wcummings 13y agoErlang's VM is very sophisticated and mature, it is at least years ahead of Go, imo. For example, compare Erlang's pre-emptive scheduling [1] to "goroutines". [1] http://jlouisramblings.blogspot.com/2013/01/how-erlang-does-scheduling.html http://jlouisramblings.blogspot.com/2013/01/how-erlang-does-...
- chimeracoder 13y ago> it is at least years ahead of Go, Yes, Erlang has admittedly had decades to improve the scheduler (versus a couple of years for the gc compiler in Go), so this is quite literally true. However, you should know that goroutines are pre-emptively scheduled now; the "scare quotes in your comment seem to imply that they aren't: http://golang.org/doc/go1.2#preemption http://golang.org/doc/go1.2#preemption
- shanemhansen 13y agoI'm a go fanboi, but to be fair, goroutines are now more preemptive, but not completely. In practice that means that if you call a function somewhere in your infinite loop, you'll get preempted. It's still possible for a single goroutine to steal an os thread. Practically speaking though, I feel like nobody should be scared away from go due to it's lack of full pre-emption. Seriously, don't write an infinite loop with no function calls.
- deleted 13y ago[deleted]
- mkhattab 13y agoPerhaps even more impressive is that it was written by an Erlang novice. This makes me want to hit the books and start learning Erlang again.
- atilaneves 13y agoHe's an Erlang novice, but the guy is the best programmer I've met. I have no doubts that if he chose to pick up D instead he'd've written code as fast as mine.