In order to perform system performance profiling using the ChorusOS
Profiler, a ChorusOS target system must include the
NFS_CLIENT feature options.
Launch the performance profiling server (the
actor) dynamically, using:
% rsh -n target arun PROF &
If you require full report forms, the profiled components must be compiled using the performance profiling compiler options (usually, the -p option).
If you are using the imake environment provided with the ChorusOS operating system, you can set the profiling option in the Project.tmpl file if you want to profile the whole project hierarchy, or in each Imakefile of the directories that you want to profile if you want to profile only a subset of your project hierarchy. In either case, add the following line:
You can also add the performance profiling option dynamically by calling make with the compiler profiling option:
% make PROF=-p
in the directory of the program that is to be performance profiled.
In this section, it is assumed that the application consists of a single supervisor actor, the_actor, it is also assumed that the target system is named trumpet, and that the target tree is mounted under the $CHORUS_ROOT host directory.
In order to be performance profiled, an application may be either:
launched at system boot time, as part of the system image, or
dynamically launched using the arun service, using the -k option, with the following command:
% rsh trumpet arun -k "the_actor"