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

RE: Memory allocation jump after running for a while with a large number of threads



These memory blocks are clearly java stack. The 32KB are used
for thread, the 992KB are stack lazy expanded. I can bet this
is IBM JVM. The problem you have is probably caused by some
jvm algorithm used for stack management.

The most common scheme is to use large stack for first xxx
number of thread, and use smaller stack for the rest. The
number you gave is not insane in this context.

Hong

> -----Original Message-----
> From: Ulrich Drepper [mailto:drepper redhat com]
> Sent: Wednesday, February 19, 2003 12:43 AM
> To: phil-list redhat com
> Subject: Re: Memory allocation jump after running for a while with a
> large number of threads
> 
> 
> Hui Huang wrote:
> 
> > [...]
> > bdf00000 (32 KB)       rw-p (00:00 0)
> > bdf08000 (992 KB)      ---p (00:00 0)
> > be100000 (32 KB)       rw-p (00:00 0)
> > be108000 (992 KB)      ---p (00:00 0)
> > be300000 (32 KB)       rw-p (00:00 0)
> > be308000 (992 KB)      ---p (00:00 0)
> > be500000 (32 KB)       rw-p (00:00 0)
> > be508000 (992 KB)      ---p (00:00 0)
> > be700000 (32 KB)       rw-p (00:00 0)
> > be708000 (992 KB)      ---p (00:00 0)
> > [...]
> 
> The permission would indicate it's used for the stack guard.  Does the
> JVM set a stack guard size?  I'll take a look to see whether there can
> be a reason for using such a guard size (note: 992 + 32 = 
> 1024).  Maybe
> some kind of overflow.
> 
> -- 
> --------------.                        ,-.            444 
> Castro Street
> Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 
> 94041 USA
> Red Hat         `--' drepper at redhat.com 
> `---------------------------
> 
> 
> 
> -- 
> Phil-list mailing list
> Phil-list redhat com
> https://listman.redhat.com/mailman/listinfo/phil-list
> 





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