Engineer. Go. Working on 
Amazing GC pause time improvements in Go 1.5.pic.twitter.com/4QBb8cNySb
-
Excited to canary Go 1.7! Continued improvement in GC pause, and improvements in various request latencies/perf!pic.twitter.com/hIMOona3tt
SUB. MILLISECOND. PAUSE. TIME. ON. AN. 18. GIG. HEAP. (Trying out Go 1.8 beta 1!)pic.twitter.com/sJhW2AC7gg
-
-
1.9rc2 canary: sub-millisecond pause time GC (18GB heap). Same as 1.8.3. If you're not on 1.8.3, upgrade or try 1.9rc2.pic.twitter.com/RX4CPOcxaW
-
Go 1.10rc1 canary: no significant performance change observations - GC pause, request latency, CPU usage all effectively the same as 1.9.
- 1 more reply
New conversation -
-
-
thou shalt label thine axes!
-
sorry! It sort of is (in the graph title), but - Y: ms, X: time of day (hours:minutes)
. I'll try to make sure I do next time.
End of conversation
New conversation -
-
-
dude stop you can’t get introspection from open source time-series dbs didn’t you get the memo
-
my fax machine broke no memos received
- End of conversation
New conversation -
-
-
How's CPU usage -vs- 1.7.3?
-
On this particular service, properly scaled for what it does: Not very different. Here's an imprecise measurement on Linux/amd64:pic.twitter.com/Zw0oBgFw4U
-
Thanks! Well done
@golang!
End of conversation
New conversation -
-
-
that is one huge heap
-
Yup. Cache data to answer requests from some odd billions of mobile devices
End of conversation
New conversation -
-
-
How's 1.9 looking?
-
Hey there. I've been canarying 1.9rc2, and AFAICT, performance for *my service* is very similar to 1.8.3. Most graphs show no +/- change.
-
Very cool, very appreciated!
End of conversation
New conversation -
-
-
Amazing!
@kellabyte do we now have your permission to a use a GC'd language? :) -
Nope, not yet. Test 128GB and 256GB heaps. 18GB is way too small :)
-
What do you do that (a) produces 256 GB of heap and (b) shouldn't be in a distributed cluster?
-
in-memory database that is distributed in a cluster. Each machine has 256GB of memory.
-
Well, that would do it :P
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.