On Jan 17, 2008 3:36 PM, yitzle <[EMAIL PROTECTED]> wrote:
> DumpSizes tells me I'm only using around 200KB RAM.
> Yet top reports close to 10MB, mostly in the DATA segment.
> Where is that memory going? Is it probably the includes? I don't see
> where else it can be.
As it runs, your perl binary
Hi. Sorry for resurrecting such an old conversation.
I don't have any Objects, so I don't think I can have any cycles.
DumpSizes tells me I'm only using around 200KB RAM.
Yet top reports close to 10MB, mostly in the DATA segment.
Where is that memory going? Is it probably the includes? I don't see
From: yitzle <[EMAIL PROTECTED]>
> Hi.
> I've got two scripts I am running and they both consume large amounts
> of memory (10MB).
> How would I go about finding where the memory is being used and
> figuring out how to reduce the memory footprint.
>
> Both scripts start off with:
>
> #!/usr/bin/p
On Jan 3, 4:10 am, [EMAIL PROTECTED] (Yitzle) wrote:
> Hi.
> I've got two scripts I am running and they both consume large amounts
> of memory (10MB).
> How would I go about finding where the memory is being used and
> figuring out how to reduce the memory footprint.
>
> Both scripts start off with
> if this mail lives in a file, then you can simply check the file
> size, perhaps with the file test operator -s.
>
> my $size = -s $file;
>
> see the section of the perlfunc manpage that talk about these:
>
Nope, unfortunately it's not in a file. The script is used as a
sendmail alias (
In article <002301c135cd$9ada2540$025a@drevlin>,
[EMAIL PROTECTED] (Brian) wrote:
> But, I'm not slurping it all at once (going line by line), which allows
> for me to check the size as I go. If somebody sends a 40 meg message,
> I'd like to catch it early before the server has a heart atta
At 02:15 PM 5/23/01 +0530, baby lakshmi wrote:
>hi
>I would like to know which part of my program is taking much time. IS that
>possible?
>if possible, can u tell me how to do it??
Oops, I just caught the subject. Your subject liine refers to memory
usage. Your text refers to time. Which is
That doesn't let you know which *part* of your program is taking the most time. For
that, try using the Devel::DProf or Devel::SmallProf debugging modules. For example,
you can do this:
perl -d:DProf myprog.pl
dprofpp
...to get a list of the 15 most intense calls.
SmallProf gives you a finer
Here's something to get you started:
perldoc -q profile
perldoc -q memory
> hi
> I would like to know which part of my program is taking much time. IS that
> possible?
> if possible, can u tell me how to do it??
> Thankyou
> regards
> babylakshmi
The benchmark perl module is what you'd be after
http://search.cpan.org/search?mode=module&query=Benchmark
install then
10 matches
Mail list logo
