News for hackers. Stuff that matters.
Re:Why Go and Not Rust? by Thaxll on Monday September 16, 2019 @10:40AM (#20984503)
"beating Go by an order of magnitude."

This is not what happend, Go was faster until batch size was > 16 then C# took over, but still C# latency was 2-3x higher than Go in every benchmarks.

Also C# / Java had to use C code where the Go driver was pure Go.

https://github.com/ixy-languages/ixy-languages/raw/master/im...

https://github.com/ixy-languages/ixy-languages/raw/master/im...

At 20Mpp/sec the C# latency was no longer on the graph:

https://github.com/ixy-languages/ixy-languages/raw/master/im...

Re:Why Go and Not Rust? by tedunangst on Monday September 16, 2019 @10:47AM (#20984581)
I think it's fascinating that someone could look at those graphs and come away with the conclusion that c# is an order of magnitude faster than go.
Re:Why Go and Not Rust? by zeeboo on Monday September 16, 2019 @10:58AM (#20984709)
On the repo page, there’s a latency graph, and on it there are two green lines. One is for Javascript and has poor latencies. The other is Go and has some of the best latencies. Because the Go one is clustered with other overlapping lines, I think people often misinterpret the Javascript line as the Go line.

https://github.com/ixy-languages/ixy-languages

Re:Why Go and Not Rust? by joelfolksy on Monday September 16, 2019 @06:57PM (#20989400)
It's also fascinating that someone could look at those graphs and say that "Go was faster until batch size was > 16 then C# took over," when Go was barely faster but C# was significantly faster.
Re:Why Go and Not Rust? by leshow on Monday September 16, 2019 @12:14PM (#20985567)
Well, in my defense, I wasn't looking at the graph when I wrote that, I was trying to remember a graph that I saw a week ago.
Re:Why Go and Not Rust? by pjmlp on Monday September 16, 2019 @01:55PM (#20986775)
C# had to use C code due to lack of .NET knowledge of the authors as discussed on the other thread.
Re:Why Go and Not Rust? by Thaxll on Monday September 16, 2019 @03:55PM (#20987948)
Would be interesting to get a PR then and see the difference.
Re:Why Go and Not Rust? by pjmlp on Tuesday September 17, 2019 @01:11AM (#20991798)
If you go to the other thread someone posted a GitHub gist showing how to use mlock() from C#, which apparently was impossible to do.
Re:Why Go and Not Rust? by joelfolksy on Monday September 16, 2019 @06:53PM (#20989373)
There would be 20 fewer lines of C?
Re:Why Go and Not Rust? by thelazydogsback on Monday September 16, 2019 @02:11PM (#20986935)
Yes, interop and Span<> should be fine...
Re:Why Go and Not Rust? by c0ff33 on Monday September 16, 2019 @10:50AM (#20984597)
As if you have a choice to not use pure Go code, it doesn't play nice with C.
Re:Why Go and Not Rust? by tfha on Monday September 16, 2019 @10:58AM (#20984707)
Cgo is a very well supported paradigm and many projects use cgo copiously.