[go-nuts] Why does a "concurrent" Go GC phase appear to be stop-the-world?

2016-10-19 Thread Will Sewell
Hey, I previously posted this on StackOverflow, but I was told this mailing list would be a better forum for discussion. I am attempting to benchmark the maximum STW GC pause time for different numbers of heap objects. To do this I have written a simple benchmark that pushes and pops messages f

[go-nuts] Re: Why does a "concurrent" Go GC phase appear to be stop-the-world?

2016-10-20 Thread Will Sewell
1.5–1.7, > and is fixed in tip (via CL 23540). > > Do you still see the problem if you run the program with the current > development version of Go? > > On Wednesday, October 19, 2016 at 6:10:23 AM UTC-7, r...@golang.org wrote: >> >> This is likely 23540 <https://

[go-nuts] Re: Why does a "concurrent" Go GC phase appear to be stop-the-world?

2016-10-26 Thread Will Sewell
h the execution tracer, but it's not an > easy tool to use. See package "runtime/trace" and the command "go tool > trace" for some hints. Issue 16528 includes some screenshots of the tool. > > On Thursday, October 20, 2016 at 6:36:27 AM UTC-7, Will

[go-nuts] Re: Why does a "concurrent" Go GC phase appear to be stop-the-world?

2016-10-27 Thread Will Sewell
addressed the issue? I'm sure > Rick and Austin would appreciate the feedback. > > On Thursday, 27 October 2016 01:46:47 UTC+11, Will Sewell wrote: >> >> Thanks for the information. I think it could well be caused by that. >> Below is the screenshot of one of the pe

[go-nuts] Re: Why does a "concurrent" Go GC phase appear to be stop-the-world?

2016-12-01 Thread Will Sewell
, please let me know. On Thursday, 27 October 2016 17:58:30 UTC+1, Dave Cheney wrote: > > Thanks for confirming that CL 23540 has reduced STW delays. > > On Friday, 28 October 2016 03:52:29 UTC+11, Will Sewell wrote: >> >> Are you referring to https://go-review.google

[go-nuts] [blog post] go tool trace: Golang's hidden trace visualiser

2017-04-06 Thread Will Sewell
Hi, I've just written a blog post/tutorial on Go's relatively unknown, but incredibly useful, trace visualiser: `go tool trace`. The post provides a tour of the interface, and examples of the kind of problems it can aid in tracking down. I was originally made aware of it by Rhys Hiltner in my p

[go-nuts] Re: [blog post] go tool trace: Golang's hidden trace visualiser

2017-04-06 Thread Will Sewell
Apologies. I just realised I didn't actually link to the post! It's here: https://making.pusher.com/go-tool-trace/. On Thursday, 6 April 2017 17:29:22 UTC+1, Will Sewell wrote: > > Hi, I've just written a blog post/tutorial on Go's relatively unknown, but > incred

Re: [go-nuts] Re: [blog post] go tool trace: Golang's hidden trace visualiser

2017-04-07 Thread Will Sewell
Thanks! I hadn't realised the compatibility issues when I wrote the post. It does seem like it's essentially seem like it's WebKit only. See: https://github.com/catapult-project/catapult/issues/100. I'm surprised it doesn't work in Safari for that reason; maybe it's the specific version you're

[go-nuts] [video] Golang's Realtime Garbage Collector

2017-04-12 Thread Will Sewell
My colleague Jim, and I, presented this video on Go's realtime GC at The Realtime Guild in London. In the first half of the talk, Jim steps through an animation of the tricolor mark and sweep algorithm. In the second half I explain a benchmark we created to measure worst case pause times and loo