🚀 go-pugleaf

Eugen Mihailescu <eugen.mihailescu@em-quicksoft.com> wrote:
[snip]
> JRE1.3.1+our jars. The thing is that launching the application with
> 'javaw.exe -classpath "REQUIRED_LIBS1;REQUIRED_LIBS2;...REQUIRED_LIBSn"' the
> application executes successfuly. Till here everything is just fine. But
> checking the amount of memory it takes I was surprissed to se that initialy
> is about 18-20 MB and during the day, when the user is using the app. it
> takes more than 40-75 MB of RAM. What is doing the garbage collector? I was
> expected that all the objects destroyed by application will be released from
> memory, in this way the amount of memory used by the application can be
> restored to a decent size for the client machine.

Not necessarily.  The JVM launches with a number of default values assigned
for heap management, including max size, initial size, and a few others.
As long as there is sufficient heap available, the gc may never be triggered
at all.  GC behavior is JVM-dependent.  Here's a link about the Sun
JVM and how it behaves when running JBuilder in it:

 http://community.borland.com/article/0,1410,23022,00.html
 
You should be able to apply these ideas to turn your own application as well.



-- 
Joi Ellis (TeamB)               http://www.teamb.com/
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Guidelines: http://www.borland.com/newsgroups/guide.html
Only posts which violate the rules in guide.html are subject to cancelation.