By default, Quantify monitors the activity of your program's threads and fibers at one-second intervals while the program is running. To pause thread and fiber monitoring, right-click in the Threads tab of the Run Summary window and select Sample Thread Status from the shortcut menu. Quantify stops monitoring threads and fibers. To resume monitoring, select Sample Thread Status again.
Notes:
§ Quantify labels threads with the name of the thread start function and a sequence number, for example: .<StartFunctionName>_<OrdinalNumber>.; or, when debug symbol information is not available for a function, .thread_<OrdinalNumber>. If your application launches threads in a non-deterministic order, Quantify may not be able to match identical threads when you compare runs. To ensure that measurement data is correctly compared between program runs, use the Rename Thread dialog box while your program is running to assign special names to the threads you are interested in.
§ If you break in a debugger while profiling a program, Quantify continues to indicate that the program is running and that threads and fibers are active. Do not set breakpoints or otherwise stop program execution, as this can produce invalid timing results.
§ If the program you're profiling uses a large percentage of your machine's RAM, monitoring threads and fibers can slow the program due to paging effects.
§ When you pause thread and fiber sampling, Quantify continues to record performance data.
(C) Copyright IBM Corporation 1993, 2009.