Also, remove any reports that are less than 1% of the total time - much easier to see the dominators.
> On Jan 14, 2019, at 6:42 PM, robert engels <[email protected]> wrote: > > I think the tree view rather than the graph would be easier to understand. > >> On Jan 14, 2019, at 6:34 PM, Kostis Kaffes <[email protected] >> <mailto:[email protected]>> wrote: >> >> Thanks! I have tried the per thread option. Attached you will find a call >> graph and see what I mean by convoluted. There are also some unknowns that >> do not help the situation. >> >> I am using the in-process transport in order to avoid being dominated by IO. >> My goal is to see if it is feasible to lower gRPC latency to a few μs and >> what that might require. >> Hence, even small overheads might matter. >> >> On Monday, January 14, 2019 at 4:16:21 PM UTC-8, robert engels wrote: >> But I will also save you some time - it is a fraction of the time spent in >> IO - so don’t even both measuring it. gRPC is simple buffer translation at >> its heart - trivially simple. >> >> MAYBE if you had a super complex protocol message you could get it to >> register CPU time in those areas with any significance in compared to the IO >> time, but doubtful. >> >> By IO time, I mean even on a local machine with no “physical network”. >> >> Any CPU time used will be dominated by malloc/free - so a no dynamic memory >> messaging system will probably out perform gRPC - but still it will be >> dominated by the IO. >> >> This is based on my testing of gRPC in Go. >> >> >> >>> On Jan 14, 2019, at 6:11 PM, robert engels <ren...@ <>earthlink.net >>> <http://earthlink.net/>> wrote: >>> >>> If you use the “perf report per thread” you should have all the information >>> you need, unless you are using a single threaded test. >>> >>> Stating “convoluted” doesn’t really help - maybe an example of what you >>> mean? >>> >>>> On Jan 14, 2019, at 5:59 PM, Kostis Kaffes <kka...@ <>stanford.edu >>>> <http://stanford.edu/>> wrote: >>>> >>>> Hi folks, >>>> >>>> As part of a research project, I am trying to benchmark a C++ gRPC >>>> application. More specifically, I want to find out how much time is spent >>>> in each layer of the stack as it is described here >>>> <https://grpc.io/blog/grpc-stacks>. I tried using perf but the output is >>>> too convoluted. Any idea on tools I could use or existing results on this >>>> type of benchmarking? >>>> >>>> Thanks! >>>> Kostis >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "grpc.io <http://grpc.io/>" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to grpc-io+u...@ <>googlegroups.com <http://googlegroups.com/>. >>>> To post to this group, send email to grp...@ <>googlegroups.com >>>> <http://googlegroups.com/>. >>>> Visit this group at https://groups.google.com/group/grpc-io >>>> <https://groups.google.com/group/grpc-io>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/grpc-io/26259f10-a18c-45c1-a247-5356424bd096%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/grpc-io/26259f10-a18c-45c1-a247-5356424bd096%40googlegroups.com?utm_medium=email&utm_source=footer>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "grpc.io <http://grpc.io/>" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to grpc-io+u...@ <>googlegroups.com <http://googlegroups.com/>. >>> To post to this group, send email to grp...@ <>googlegroups.com >>> <http://googlegroups.com/>. >>> Visit this group at https://groups.google.com/group/grpc-io >>> <https://groups.google.com/group/grpc-io>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/grpc-io/C296B1F6-90D7-451A-A6FB-A8E909AB40B4%40earthlink.net >>> >>> <https://groups.google.com/d/msgid/grpc-io/C296B1F6-90D7-451A-A6FB-A8E909AB40B4%40earthlink.net?utm_medium=email&utm_source=footer>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "grpc.io <http://grpc.io/>" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> Visit this group at https://groups.google.com/group/grpc-io >> <https://groups.google.com/group/grpc-io>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/grpc-io/587f4e91-c3fc-4f56-96a2-81755f8efe72%40googlegroups.com >> >> <https://groups.google.com/d/msgid/grpc-io/587f4e91-c3fc-4f56-96a2-81755f8efe72%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> <output.png> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5CC9C46E-37B2-4D11-BB45-72C8F85BA4A5%40earthlink.net. For more options, visit https://groups.google.com/d/optout.
