Re: [go-nuts] Re: Using Context to store TraceIDs

t; > That's my own 2 cents anyway. -Daniel > > On Tuesday, May 30, 2017 at 8:39:18 AM UTC-7, William Kennedy wrote: > After reading this: > https://cloudplatform.googleblog.com/2017/04/distributed-tracing-for-Go.html > <https://cloudplatform.googleblog.com/2017/04/d

[go-nuts] Re: Using Context to store TraceIDs

After reading this: https://cloudplatform.googleblog.com/2017/04/distributed-tracing-for-Go.html I can see how the Context is being used, through a separate API. Would it make sense to use a separate Context value for the "Trace" Context and use a separate Context value for the "Cancellation" C

[go-nuts] Using Context to store TraceIDs

I read this post by Jaana https://docs.google.com/document/d/1GFHAksL5HQy1YacCFXMUdOTC4e21uoX-TbMzRXAtx_I/preview I wanted to start a conversation about the Context value bag and TraceIDs. I am concerned with the idea of using the Context to pass TraceIDs into the API of packages that don't dire

[go-nuts] Re: Getting a snapshot of point-in-time allocation

I have an example in the training of taking two profiles and using this option to compare them. I would love any feedback you have on the content in this topic or what you think might be missing. Thanks https://github.com/ardanlabs/gotraining/tree/master/topics/profiling -- You received this m

[go-nuts] Just because we can add multiple logical processors for the scheduler to use doesn’t mean we should

There are many factors that will determine how well your program performs. There are no guarantees that using more threads or goroutines is going to yield better performance. Sometimes throwing more threads or goroutines at a problem can slow things down. It really depends on the work you are do