On 7/28/05 2:21 AM, "Kari Lavikka" <[EMAIL PROTECTED]> wrote:
There's a new profiling tool called oprofile: http://oprofile.sourceforge.net/download/ that can be run without instrumenting the binaries beforehand. To actually find out what the code is doing during these stalls, oprofile can show you in which routines the CPU is spending time when you start/stop the profiling. As an alternative to the "guess->change parameters->repeat" approach, this is the most direct way to find the exact nature of the problem. - Luke ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
