On Tue, Jan 26, 2016 at 5:11 PM, Garrett D'Amore <garrett@xxxxxxxxxx> wrote:
Go uses a GC, its true. However, mangos itself is designed to avoid
hitting the GC whenever possible, through the use of buffer caching and
recycling/reuse.
My own latency measurements show that mangos performs comparably to
nanomsg. In some tests it does better, in others worse, but the
differences are generally small.
Now, if your *application* hits the GC hard, then you’re going to have
problems. But it is possible to preallocate your own memory and avoid the
GC. You just have to manage your own allocations then, just like you do in
C.
Now that said, Go’s GC has improved a lot in the last releases, so you
probably won’t see it do too badly.
I also know a lot of low latency applications (HFT) are written in Java.
You might want to recheck some of your assumptions.
