For C/C++ and other languages there are lots of profiling tools available, but getting them to work with PDL code is a real problem.
The best profiling tool I've seen is AMD's CodeAnalyst (which is free* **. *if you sign a NDA, **and can get it to compile on your system). That software only works if you have an AMD chipset, but it requires very little knowledge of the code to work properly. The AMD Opteron has tons of performance instrumentation on-chip, so the CodeAnalyst mainly uses that and a normal decompiler to show you how the code was translated to asm, and how much time has been spent on each line. It also helps if your perl exe and libs have been compiled with -g so you can check out that portion of the code. It's worth a shot if nobody else here has tried it already. -Judd On Fri, 2007-01-12 at 07:18 -0500, zentara wrote: > On Fri, 12 Jan 2007 07:37:24 +0000 > "Xavier Calbet" <[EMAIL PROTECTED]> wrote: > > > Zentara, could you provide me with the command you > >used to find out cpu time and mem so I can run > >a similar test and compare with your results? > > Thanks, > > Xavier Calbet > > The simplest way is to launch a separate process running 'top', > and each second it will report cpu and memory for the process. > > You can also speed top up, to update faster than each second, > and you can specify only one pid to watch(if you don't like the listing). > Google for "top command". > > I could probably be automated and integrated into the test program, > but doing so would be more complicated than the test itself. > > zentara > -- ____________________________ Judd Taylor Software Engineer Orbital Systems, Ltd. 8304 Esters Blvd, Suite 870 Irving, TX 75063-2209 [EMAIL PROTECTED] (469) 442-1767 x127 _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
