Hi Ken, If you have a CINT script myscript.C, you can execute it using compiled code instead of interpreted code via .x myscript.C+ To do this, your file myscript.C must be a compilable C++ file with all the include statements necessary. In case, you already run with compiled code, you can profile your application by compiling your code with option "pg" if you run with gcc, then use gprof to show the classes/functions where you spent the time. To use this option, your code must be linked statically (not in a shared lib). We provide a build option for ROOT (make -static) that creates a single archive library libRoot.a that you can use in case you want to profile the time spent in ROOT classes, otherwise you just need to link statically your classes. Ken Bloom wrote: > > Dear ROOTers, > > I have written a lot of code that is compiled with CINT and then > executed within ROOT. I think that it takes too long to run (OK, I'm > impatient), and would like to speed it up. Are there any tools that would > allow me to see where my CPU time is being spent? Thanks, best wishes. > > Ken > > ------------------------------------------------------------------------------ > Ken Bloom, Karma Adjuster Department of Physics > 734-763-2329 / 734-936-1817 (fax) University of Michigan > kenbloom@umich.edu http://www.umich.edu/~kenbloom
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:13 MET