IIRC, -XX:MaxPermSize=256m sets the max size of the perm generation.  
Wouldn't -Xmx640m set the max size?

http://www.petefreitag.com  and http://www.bpurcell.org/blog has some
good stuffs on this.  There is a macromedia tech note on performance
too...I don't have that handy though.

Doug


On Tue, 05 Oct 2004 08:08:44 -0700, Lawrence Ng <[EMAIL PROTECTED]> wrote:
> I'm not sure this helps but may be related with how Windows manages
>  memory
>  
>  I found that Windows doesn't really USE all the RAM we give it very
>  much - that's why it doesn't seem to care.  I experienced this with my
>  laptop - it was fine under Windows but when I started using VMWare and
>  had a few different virtual sessions running at once it started giving
>  me memory errors.  Just Windows on its own never even tried to access
>  the upper ranges of his RAM. ..
>  
>  
>  Linux by contrast will use ALL available memory - what isn't needed for
>  programs is used to cache frequently accessed files from disk.
>  
>  Because of this, that may be why you're/we're getting memory
>  inconsistencies...
>  
>  I'm probably way off base so excuse me if I'm not helping any =)
>  
>  cheers...
>  
>  
>  Kingston is pretty good about replacing memory no questions asked.  So
>  I'll try and exchange it again.________________________________
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to