[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question about top



Yes, I have a huge array of pointers to class objects, each containing a
name and attribute map of the archive contents.

I actively use this map, and I'm fairly sure it gets might full.
I still don't see why ~4000 filenames (strings alloced with MAX_PATH
bytes) and their corresponding attribute bits eat up a gig and a half, and
where the non-SGI-redhat-running-on-i386 allocates this ram from. or does
it? Just how reliable is top anyway? better progs? ideas?


---= Miki Shapiro =------------------
 ---= Cell: (+972)-56-322433 =--------
  ---= ICQ: 3EE853 =-------------------
   ---= Windows Programmer in Rehab =---
    -------------------------------------

"If at first you don't succeed...
.. Skydiving is probbably not for you."

On Thu, 2 Aug 2001, Yaron Zabary wrote:

> On Thu, 2 Aug 2001, Miki Shapiro wrote:
> 
> > Hi list
> > 
> > A program I wrote (namely, an archive extraction engine), when processing
> > a big and nasty archive, drives the numbers on top/ktop nuts.
> > In the memory column, I have > 1000MB, when the machine only has 512MB RAM
> > altogether (256 physical and a 256MB swap partitition)
> > 
> > Here's what it looks like:
> > 
> > PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND
> > 
> > 23882 root    14   0 1357M 1.3G  2232 R    967M 46.2 539.4  10:09 vs
> > 
> > 1.3 Gigs?!
> > 539% memory usage?
> > 
> > ktop also says "resident" memory is ~130Megs at this stage. It still
> > sounds too large, but it's technically possible, and I could be leaking.
> > 
> > Anything about how my code allocs/deallocs that screws top completely
> > up? Ideas?
> > 
> > System is RH6.2, default kernel.
> > uname -a says:
> > Linux november 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown
> 
>   Lazy allocation ? I never heard of it available with Linux, but it is
> available with SGI systems. It means that you can malloc as much memory as
> you want and will crash when the program tries to actually use the pages
> which are not available. It creates some non-deterministic behavior
> (malloc will succeed, but the program will later crash). It is useful for
> algorithms using sparse matrix. With SGI you can disable that. Any chance
> you have a huge array ?
> 
> > 
> > Thanks!
> > 
> > ---= Miki Shapiro =------------------
> >  ---= Cell: (+972)-56-322433 =--------
> > ---= ICQ: 3EE853 =-------------------
> >  ---= Windows Programmer in Rehab =---
> >   ------------------------------------
> > 
> > "If at first you don't succeed...
> > .. Skydiving is probbably not for you."
> > 
> > 
> > =================================================================
> > To unsubscribe, send mail to linux-il-request@linux.org.il with
> > the word "unsubscribe" in the message body, e.g., run the command
> > echo unsubscribe | mail linux-il-request@linux.org.il
> > 
> > 
> 
> 
> -- Yaron.
> 
> 
> =================================================================
> To unsubscribe, send mail to linux-il-request@linux.org.il with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail linux-il-request@linux.org.il
> 


=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il