Show this thread
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
huh, Linux/arm64? On an Intel CPU?
-
My mistake, it was intel.
End of conversation
New conversation -
-
-
$ awk 'BEGIN {print "# Go 1.0 vs. 1.11 Benchmarks"} NF > 7 {print $1 "\t" substr($8,2,length($8)-2)}' go1-11.txt | sort -nr -k2|dchart -hbar -textsize=1.2 -top=90 | pdfpic.twitter.com/MiR5N1CmiH
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Expected a bigger gap, maybe the first version was already fast enough
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
oh wait, never mind, against 1.0 not 1.10
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wow impressive since 1.0 was c based
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
How does that happen? That's a pretty good text processing improvement! And gunzip...
-
Because go1.11 merged lots of Neon based optimizations.
-
See my other tweet: I didn't immediately realize it was comparing against 1.0 there. Also NEON is ARM right? The benchmark show is on an Intel i5
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.