Why not just run your code with 'perf' and look at the output? That would give you a good idea of roughly where the time is being spent. (and give you insight into how much time is spent in the kernel)
On Wednesday, August 31, 2016 at 10:17:35 PM UTC-7, Sergey Shalnov wrote: > > Let's simplify the question. > What functions are belongs to the chttp2 transport layer? > I see lot of different functions in different C sources and directories > tree. Many of them calls to each other at the same layer. > Could you recommend me which functions used as "top" interface to chttp2 > to take them into account in profiling? > Thank you > Sergey > -- 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/1d064edf-eab2-430f-a842-91baf5ca6571%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
