Joined: 23 Nov 2006 Posts: 8723 Location: 221 B Baker St
Hi Anuj,
Strobe is quite good at helping to identify bottlenecks.
If a process consistently preforms poorly, Strobe might be used to isolate where various concentrations of cpu or i/o is being used.
The job for this topic does not seem to fall in this category. With the same input, it runs for different lengths of wall-time. It does not use (from what we've seen) different amounts of resources. Which leads me to believe the difference in elapsed/wall tme is due to external influences rather than something in the code of "this" process.
