oprofile

• http://oprofile.sourceforge.net/news/^{Image Removed}

This is a sampling profiler, so it has minimal impact on Traffic Servers performance.

...

...

Google profiler

• Main Page: http://code.google.com/p/google-perftools/^{Image Removed}
• CPU Profiler: http://google-perftools.googlecode.com/svn/trunk/doc/cpuprofile.html^{Image Removed}

This too is a sampling profiler, so it has minimal impact on Traffic Servers performance.Server's performance. Support for the profiler needs to be compiled into Traffic Server for it to work. There is an option to add profiling support when running configure and is described in the steps below.

Install the Google's perftools development package, the command may vary on the OS, below is on Fedora 12:

Run configure with the option to add profiling support. It will check to see if the header and library is installed. You will have to recompile traffic server to add calling the profiler's start and stop functions.

You can either install the package with "sudo gmake install" or run the program for the current directory if you already have an installation with all the logs and configuration directories setup.

Next you will need to run your benchmark. After the benchmark is complete, kill the traffic_server process or stop traffic server with the startup script. The traffic server process will need to be shutdown before a proper profile file is written.

Now we can look at the profiling information.

To make a callgraph of the program in PDF form.

If you want to investigate a certain function you can the focus option.

Callgrind

• http://valgrind.org/info/tools.html^{Image Removed}

Callgrind is will slow down the performance of traffic server significantly.