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

[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 using. It's a shame it doesn't support wider compatibility. I 
suppose the fact the tool was originally designed to be used with the 
Chromium project implies that practically everyone using it would have been 
using Chrome/ium.

On Friday, 7 April 2017 17:49:12 UTC+1, Sam Whited wrote:
>
> On Fri, Apr 7, 2017 at 2:55 AM, Stephen Russell 
>  wrote: 
> > Fantastic blog, thank you :) just wanted to let you know the demo 
> doesn't 
> > work in safari. 
>
> Agreed; super helpful blog post, thanks again. It also doesn't work in 
> Firefox. 
>
> —Sam 
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Stephen Russell]

Fantastic blog, thank you :) just wanted to let you know the demo doesn't 
work in safari.


On Thursday, 6 April 2017 18:00:55 UTC+1, Will Sewell wrote:
>
> 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 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 previous message 
>> to this mailing list when I was investigating long GC pause times: 
>> https://groups.google.com/d/msg/golang-nuts/nOD0fGmRp_g/4FEThB1bBQAJ. So 
>> thanks for pointing it out Rhys! As he mentions in that thread, it is 
>> currently not well documented, so I felt it was a good opportunity for a 
>> blog post after playing around with it for a bit.
>>
>> In the future I'd like to investigate and write about how the runtime 
>> event system itself actually works because it seems like an interesting 
>> area.
>>
>> Let me know if you have any feedback.
>>
>> Thanks,
>> Will
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Ondrej]

Excellent stuff. I remember finding out about trace over here

https://groups.google.com/forum/#!topic/golang-nuts/Ktvua7AGdkI

and I marvelled that there wasn't any documentation, so it was all trial 
and error for me. But what a gem. What a gem. Both the tool and your blog 
post.

On Thursday, 6 April 2017 18:29:22 UTC+2, Will Sewell wrote:
>
> 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 previous message 
> to this mailing list when I was investigating long GC pause times: 
> https://groups.google.com/d/msg/golang-nuts/nOD0fGmRp_g/4FEThB1bBQAJ. So 
> thanks for pointing it out Rhys! As he mentions in that thread, it is 
> currently not well documented, so I felt it was a good opportunity for a 
> blog post after playing around with it for a bit.
>
> In the future I'd like to investigate and write about how the runtime 
> event system itself actually works because it seems like an interesting 
> area.
>
> Let me know if you have any feedback.
>
> Thanks,
> Will
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[omarshariffdontlikeit]

This is awesome. Didn't even know this tool existed!

On Thursday, April 6, 2017 at 6:00:55 PM UTC+1, Will Sewell wrote:
>
> 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 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 previous message 
>> to this mailing list when I was investigating long GC pause times: 
>> https://groups.google.com/d/msg/golang-nuts/nOD0fGmRp_g/4FEThB1bBQAJ. So 
>> thanks for pointing it out Rhys! As he mentions in that thread, it is 
>> currently not well documented, so I felt it was a good opportunity for a 
>> blog post after playing around with it for a bit.
>>
>> In the future I'd like to investigate and write about how the runtime 
>> event system itself actually works because it seems like an interesting 
>> area.
>>
>> Let me know if you have any feedback.
>>
>> Thanks,
>> Will
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Rob Pike]

That's a great blog post, Will. Thanks for that. The Go team should have
provided one for you, I must say, so double thanks.

-rob


On Thu, Apr 6, 2017 at 10:00 AM, Will Sewell  wrote:

> 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 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 previous message
>> to this mailing list when I was investigating long GC pause times:
>> https://groups.google.com/d/msg/golang-nuts/nOD0fGmRp_g/4FEThB1bBQAJ. So
>> thanks for pointing it out Rhys! As he mentions in that thread, it is
>> currently not well documented, so I felt it was a good opportunity for a
>> blog post after playing around with it for a bit.
>>
>> In the future I'd like to investigate and write about how the runtime
>> event system itself actually works because it seems like an interesting
>> area.
>>
>> Let me know if you have any feedback.
>>
>> Thanks,
>> Will
>>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 
> 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 previous message 
> to this mailing list when I was investigating long GC pause times: 
> https://groups.google.com/d/msg/golang-nuts/nOD0fGmRp_g/4FEThB1bBQAJ. So 
> thanks for pointing it out Rhys! As he mentions in that thread, it is 
> currently not well documented, so I felt it was a good opportunity for a 
> blog post after playing around with it for a bit.
>
> In the future I'd like to investigate and write about how the runtime 
> event system itself actually works because it seems like an interesting 
> area.
>
> Let me know if you have any feedback.
>
> Thanks,
> Will
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.