3 ms·
He was probably scanning elements that were larger than int32s, even on a 2013 this code would run at Gib/s. The point of my benchmark was that C is nowhere ne
by richieartoul 6y ago
He was probably scanning elements that were larger than int32s, even on a 2013 this code would run at Gib/s.
The point of my benchmark was that C is nowhere near 50-100x faster than Go and that the user I'm replying to shouldn't make unsubstantiated claims like that.
- formerly_proven 6y agoMy claim that the trivial C code is 100x faster than the number from the article is a) well substantiated b) all there is c) perfectly clear.