On Tue, May 12, 2020 at 2:17 PM Randall Becker wrote:
>
> On Tuesday, 12 May 2020 16:55:54 UTC-4, Ian Lance Taylor wrote:
>>
>> On Tue, May 12, 2020 at 1:11 PM Randall Becker wrote:
>> >
>> > I have the go repository with release-branch.go1.4 checked out on a
>> > Windows/cygwin64 installation.
To clarify, I assume you have an internal request id that is tracked (if not, I
am not sure how your logging would work). Create a label that matches the
request ID at the top handle request layer.
Then you can use pprof/trace, find that request, and do a detailed trace
analysis on the event ha
You can do it - just create a label for each request that you want timed
individually. These will be treated as distinct events.
The OS threads are shared across Go routines - so using OS thread CPU counters,
or thread monitoring won’t work.
So you use labels to track “events” - in this case an
It's not that Ian's response was clearer, it's that he actually answered
the question of if I can do $thing in Go; given that I can't he pointed me
to the same reference as you.
It's okay that Go can't do some things, but being opaque about it isn't
helpful.
Thanks for your help both of you!
-Ste
On Tuesday, 12 May 2020 16:55:54 UTC-4, Ian Lance Taylor wrote:
>
> On Tue, May 12, 2020 at 1:11 PM Randall Becker > wrote:
> >
> > I have the go repository with release-branch.go1.4 checked out on a
> Windows/cygwin64 installation. Looking for the bootstrap.bash and not
> finding one in that
In my first response I said to use labels and referred you to a document on how
to do it. I guess Ian’s wording was clearer :)
> On May 12, 2020, at 3:53 PM, Ian Lance Taylor wrote:
>
> On Tue, May 12, 2020 at 1:01 PM Steve Canfield
> wrote:
>>
>> Thanks Ian. Are there limits on how many su
On Tue, May 12, 2020 at 1:11 PM Randall Becker wrote:
>
> I have the go repository with release-branch.go1.4 checked out on a
> Windows/cygwin64 installation. Looking for the bootstrap.bash and not finding
> one in that branch. Assuming that my eventual target will be called nsx
> (rather the s
On Tue, May 12, 2020 at 1:01 PM Steve Canfield wrote:
>
> Thanks Ian. Are there limits on how many such labels exist for the life of
> the process, or can be active at once? Would labeling by rpc_guid be
> acceptable?
There are no limits on labels other than memory usage.
Ian
> On Tue, May 12
On Monday, 11 May 2020 16:37:31 UTC-4, Ian Lance Taylor wrote:
> On Mon, May 11, 2020 at 8:45 AM Randall Becker > wrote:
> >
> > I know the subject has been covered for other platforms, but this one
> (HPE NonStop TNS/X) has a few quirks.
> >
> > The platform does not support gcc at all. Ma
Thanks Ian. Are there limits on how many such labels exist for the life of
the process, or can be active at once? Would labeling by rpc_guid be
acceptable?
On Tue, May 12, 2020 at 12:06 PM Ian Lance Taylor wrote:
> On Tue, May 12, 2020 at 10:31 AM Steve Canfield
> wrote:
> >
> > I feel like I m
On Tue, May 12, 2020 at 10:31 AM Steve Canfield
wrote:
>
> I feel like I must be really dense, but it doesn't seem like you are
> answering my question.
>
> Again, assume I have good reasons to want to know the cpu usage for every
> request. Let's say I want to do isolation or billing or whateve
I feel like I must be really dense, but it doesn't seem like you are
answering my question.
Again, assume I have good reasons to want to know the cpu usage for every
request. Let's say I want to do isolation or billing or whatever on the
basis of cpu usage.
Is this possible in Go?
-Steve
On Mon
12 matches
Mail list logo
