search for: pprof

...head in posting lists). Understood. > Can prof report time for a function including things it calls? callgraph? Attached is a profile the output of "perf report -g" with callgraph info. I'm no perf expert, either, but slowly learning more as I go along... Btw, I tried google-pprof (from the Debian stable google-perftools 2.7-1 package) and couldn't figure it out... Even the example from the manpage: `google-pprof /bin/ls ls.prof` didn't seem to work. It tried to open an invalid URL with curl 'http://ls.prof/pprof/profile?seconds=30' ... *shrug*

Hey guys, I am currently working on a project that uses JIT compilation to compile incoming user requests to native code. Are there some best practises related to profiling the generated code? My project uses gperftools pprof for profiling etc. Is there a way to hook the two up? Are there any other profiling method that works? This page describes how to debug JIT code with GDB. I wonder if something similar could be done for gperftools/pprof? Regards, -- Priyendra -------------- next part -------------- An HTML attachm...

...you use MCJIT (as opposed to the older JIT) then oprofile support isn't in place yet. Both of these work by providing a JITEventListener that receives notification when new code is emitted and hooks it up to the profiling tool via some tool-specific notification API. I'm not familiar with pprof, but it probably wouldn't be very difficult to write a new event listener to add support for pprof. You can find the oprofile code in 'llvm/lib/ExecutionEngine/OProfileJIT' to use as an example. -Andy From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Beh...

...er JIT) then oprofile support isn’t in > place yet.**** > > ** ** > > Both of these work by providing a JITEventListener that receives > notification when new code is emitted and hooks it up to the profiling tool > via some tool-specific notification API. I’m not familiar with pprof, but > it probably wouldn’t be very difficult to write a new event listener to add > support for pprof.**** > > ** ** > > You can find the oprofile code in ‘llvm/lib/ExecutionEngine/OProfileJIT’ > to use as an example.**** > > ** ** > > -Andy**** > > ** ** &gt...

...477edb) built with CXXFLAGS=-ggdb3, and it's closer to 100%: https://80x24.org/spew/20200825215517.GA3936 at dcvr/2-perf-report-20200825-214820.gz The machine I'm working on is also significantly busier at the moment trying to reproduce an unrelated problem. > > Btw, I tried google-pprof (from the Debian stable > > google-perftools 2.7-1 package) and couldn't figure it out... > > Even the example from the manpage: `google-pprof /bin/ls ls.prof` > > didn't seem to work. It tried to open an invalid URL with > > curl 'http://ls.prof/pprof/profile?s...

...at it seems to be trying to show time spent in "Children", but it doesn't seem to do that completely so I'm not sure how to interpret it. I'd expect the parent of everything to show up with 100% including Children (or close to 100%) but nothing does. > Btw, I tried google-pprof (from the Debian stable > google-perftools 2.7-1 package) and couldn't figure it out... > Even the example from the manpage: `google-pprof /bin/ls ls.prof` > didn't seem to work. It tried to open an invalid URL with > curl 'http://ls.prof/pprof/profile?seconds=30' ... *...

..., one per function. If there are thousands of functions there will be thousands of files. perftools can't use the first option, since it only collects stack address information during the run. And it would be very difficult/impractical to list all (thousands) of the resulting .o files into pprof's command line. Same with valgrind and very slow to load them since pprof runs addr2line per object file. This will take forever. So option -jit-emit-debug-function-range is meant to amend the above two. It creates just one file with information just sufficient for perftools. Yuri

Have you found http://llvm.org/docs/DebuggingJITedCode.html? The JIT already has support for something like this for gdb's benefit. Perftools and valgrind just don't know how to find it yet. On Sat, Jun 19, 2010 at 2:03 PM, Yuri <yuri at rawbw.com> wrote: > This new option (--jit-emit-debug-function-range) will allow to output > function information for memory ranges that

...led 'xray-profiling'. The intent is to implement handlers that will generate profile data [3] that other tools can digest. We'll export the data in an XRay-specific format for a more compact representation. We intend to implement conversion tools to support the profile.proto format that pprof can handle as input. To do this, we need to record the "stack" of functions that are XRay instrumented, represented as a prefix tree (or forest, as we'll see later). This prefix tree will represent the XRay instrumented functions that have been entered, and then exited. A() -> B(...

...ing'. > The intent is to implement handlers that will generate profile data [3] > that other tools can digest. We'll export the data in an XRay-specific > format for a more compact representation. We intend to implement conversion > tools to support the profile.proto format that pprof can handle as input. > > To do this, we need to record the "stack" of functions that are XRay > instrumented, represented as a prefix tree (or forest, as we'll see later). > This prefix tree will represent the XRay instrumented functions that have > been entered, and th...

On Wed, Aug 27, 2014 at 4:53 PM, Chandler Carruth <chandlerc at google.com> wrote: > > On Wed, Aug 27, 2014 at 4:40 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> DW_AT_frame_base (the location of the frame pointer - is that needed for >> symbolication?) > > > I think this is used by libunwind style stack unwinders in conjunction > with

...e postlist for that term. That means during a search we end up re-fetching this separately to finding it to read the postlist, with an extra cursor seek. It would be better to just look up each term once. I think to achieve that cleanly will need a bit of refactoring. > Unfortunately, google-pprof can't seem to figure out symbols > like perf can. I had the same problem with the Debian-provided > -dbgsym packages for 1.4.11-1 as I am having with xapian.git > > Maybe I should've tried -g instead of -ggdb3? > (I've been mainly using -ggdb3 in C code for years, >...

I'm asking here, rather than R-devel, because it seems to be a Linux specific question and because I'm using Ubuntu-9.04. I'm trying to profile an package, and got errors, so I decided to follow BDR's (http://tolstoy.newcastle.edu.au/R/devel/06/02/4254.html) example exactly, and got same problem. Can anyone replicate? $ sudo mkdir -p /var/tmp//usr/lib/R/library/stats/libs $

Olly Betts <olly at survex.com> wrote: > On Fri, Aug 21, 2020 at 09:06:59AM +0000, Eric Wong wrote: > > Going back to the "prioritizing aggregated DBs" thread from > > February 2020, I've got 390 Xapian shards for 130 public inboxes > > I want to search against(*). There's more on the horizon (we're > > expecting tens of thousands of public