Robert Killheffer wrote:> I'm testing several different algorithms for performing the same task, and> I'm wondering if there is some way I can tell
- from within each version of> my script - how much memory and CPU time the script uses each time it runs.> > > > I would like to be able
to output
duled tasks> under the Windows scheduling system. Can I use the
time command in that> context? Perhaps through a system call from the script? Like I said, I'd> like to be able to gather this data automatically while the script
is> running, and output it to a log each time.> > - R
On XP (and I think on 2000) there are standard command-line tools for
this; 'tasklist' will list all the processes, and 'taskkill' will kill a
specified one.
Both are normally installed in c:\windows\system32
Dan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Be
My work system was recently "upgraded" to Windows 7 and ActivePerl 5.14.2 - I
had been using v5.8 + PDK v6 for years. Unfortunately, the old 32-bit PDK
doesn't work with my company-provided install of 5.14.2. In addition, the
Devel::ptkdb module is not available for 5.14.
I've been using the
u must have some
> setting present that prevents this.
>
> On 19/03/2012 10:15, Daniel Rawson wrote:
>> My work system was recently "upgraded" to Windows 7 and ActivePerl 5.14.2 -
>> I had been using v5.8 + PDK v6 for years. Unfortunately, the old 32-bit PDK
>> do
independent, whereas everything labeled a "deployment
> tool" has code that needs to be adapted to each Perl release).
>
> Cheers,
> -Jan
>
> On Mon, 19 Mar 2012, Daniel Rawson wrote:
>> Mark -
>>
>> Thanks . . . I get the command-line debugger when I star
vePerl, even though PerlApp& friends won't
>> (I can't remember what was included in PDK 6, but generally
>> everything that was labeled a "productivity tool" should be
>> version independent, whereas everything labeled a "deployment
>> tool&
03/19/12 01:32 PM, Jan Dubois wrote:
> On Mon, 19 Mar 2012, Daniel Rawson wrote:
>> Chris -
>>
>> That's what I was afraid of . . . .my 5.14.2 install is definitely
>> 64-bit, but the old PDK is from 2004, so it's certainly 32-bit :-(
>
> The 32-bit PDK
