• in the cfg file something like this:
service = ProfilerService {
       untracked int32 firstEvent = 2
       untracked int32 lastEvent = 51
       untracked vstring paths = { "p1"}
  • to run valgrind
valgrind --tool=callgrind --combine-dumps=yes --instr-atstart=no --dump-instr=yes --separate-recs=1 cmsRun ****.cfg
  • use kcachegrind to interpret the valgrind output

Its name is callgrind.out... ending with the PID of the job. You may need to add something to your path, similar to the example

      setenv PATH /afs/cern.ch/cms/bin/i386_linux2:${PATH}
      kcachegrind callgrind.out.xxxxx
-- UrsulaBerthon - 26 Feb 2008
Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2008-02-26 - UrsulaBerthon
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback