Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#1707 closed enhancement (implemented)

We need a howto for running oprofile properly

Reported by: nickm Owned by: weasel
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I hear that we don't have a good description of the best way to oprofile Tor and get useful results. It would be great to have a patch to doc/HACKING explaining how to do this. Weasel said that he could, if he were reminded. This task exists to remind him.

Child Tickets

Change History (6)

comment:1 Changed 9 years ago by nickm

Status: newassigned

Assigning this task to weasel to remind him even better. :)

comment:2 Changed 9 years ago by weasel

<weasel> - build tor with debugging symbols (you probably already have)
<weasel> - build all the libraries you care about with debugging symbols (probably you only care about libssl, maybe zlib)
<weasel> - copy this tor to a new directory
<weasel> - copy all the libraries it uses to that dir too (ldd ./tor will tell you)
<weasel> - set LD_LIBRARY_PATH to include that dir. ldd ./tor should now show you it's using the libs in that dir
<weasel> - run that tor
<weasel> - reset oprofiles counters/start it
<weasel> - after a while, have it dump the stats on tor and all the libs in that dir you created.
<weasel> - profit
<Sebastian> Is there a reason not to care about libevent?
<weasel> don't know
<weasel> your profile will tell you afterwards

comment:3 Changed 9 years ago by nickm

Added an initial version to doc/HACKING based on weasel's comments and my vague recollections of using opcontrol/oprofile.

comment:4 Changed 9 years ago by nickm

Resolution: implemented
Status: assignedclosed

Closing as "good enough for now"

comment:5 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:6 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.