I've never done anything like this on Windows, but a hunt around CPAN comes up with Win32::SystemInfo. If this doesn't meet your needs, why not use an external tool to monitor your process? Does WinCE have the Windows Task Manager, and if so would that be any use?

In general, I'd recommend BSD::Resource for this, but I doubt it will work on WinCE.

Thank you for interesting input, and sometimes your approach this will work good. But I am trying to find less platform-dependent (WinCE is just an example!) but rather Perl-specific solution, something similar to Devel::Prof or even DB::DB modules.

I think best solution will be an XS module that understands Perl internals and provides information, but I am lost whether such exists, or can be written without changing the Perl core.

BTW will BSD::Resource work for Linux? for Win32?

Typing BSD::Resource linux into Super Search comes up with Re: How to limit resources ?.

I can't find anything that suggests BSD::Resource runs under Windows. Activestate ship PPMs for Linux and Solaris but not Windows, which suggests it won't run there. However, it seems cygwin might support getrlimit (getrlimit is the system call that BSD::Resource uses to retrieve information).

I ended up relying on the Windows Task Manager to monitor mine. Nobody mentioned a way to do it within the script, though. Sounds like *that* is what you want.

Yes, that link has some related information, including
(but not limited to :)
- PERL_DEBUG_MSTATS
- perl -V:d_mymalloc

I will use those in my case.

It's pity that perl does not have a possibility to acquire such information during execution (AFAIK, Java hase one, but I'm not sure). But I can live without that information provided I have great speed gains for ordinary programs execution :)
Vadim

=item *

Devel::Peek now has an interface for the Perl memory statistics
(this works only if you are using perl's malloc, and if you have
compiled with debugging).
[download]

So, if one interested in such statistic, (s?)he should recompile perl with debugging and perl-malloc options.

A bit pity that this is not available in standard executables, or at least without -DDEBUGGING, but it is good to have such possibility at all.

Many thanks to all who helped me with this,
Vadim.