Max possible heap size?

Hello!
I'm looking for some informations about the maximum possible heap size for the JVM. Is it possible to increase the heap size to 4 GB or more, if the system has 4GB or more RAM)? At the moment I have problems to increase above 2 GB. (System: Intel 64bit CPU, 4 GB RAM, Suse Linux 9.0, JVM 1.4.2)
Thanks,
Christian

Seems 3GB is the max: http://docs.sun.com/source/819-0084/pt_tuningjava.html search for "linux".
If you can't get past 2GB, there are several possibilities. "man ulimit" (or "limit" in some shells) comes to mind first.
Also check out http://forum.java.sun.com/thread.jspa?threadID=603239

Similar Messages

Equium M70: What is a max possible HDD size

Hi..
Does anyone know what is the maximum size hard drive this laptop can take.
It currently has a 40GB hard drive and i would like a larger one but am unsure what size i should get.

Hi
Ive found this forum thread;
http://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=93195&#93195
the guy have an Sat M70. Its very similar to the Equium M70 series.
He was able to upgrade the M70 with the 160GB HDD. So it looks like its possible to use such big HDDs on the M70 notebooks.

Optimum Max JVM Heap Size Question

I saw Ken running around, so I figured this would be a good
time to post.
I am running CF 6.1, Windows 2003 Server, IIS 6.0, SQL2003;
all are on the same machine.
This machine is a web-server that runs this particular
ColdFusion application ONLY. Nothing else.
I have looked through a decent amount (although I'm sure not
all) of the white papers on this setting. I have left it at 512MB,
but since I have 2GB on the server, I thought about increasing it,
but didn't know how much CF would really use, if it would increase
garbage collection times, etc.
So once my brain finally said "I don't know", I thought I'd
post on it.
Thanks,
Mike

Yeah, I gathered it was an art.
Stability/performance has been a minor factor - the SQL
database referenced by the datasource is on the same box, and I
still get the occassional "datasource went by-by" (i.e. - timeout
on dsn) error. It seems to occur during peak load times (peak query
load, that is). Disk activity goes pretty high at those times, as
well.
I was kind of going with the "better from memory than from
disk" idea, but didn't know if this was a dance with other settings
(i.e. - max queries, etc.).
Sounds like it is - so I will start (gently) changing a few
parameters to see if I can get those DSN lost errors to be
extremely infrequent.
I really appreciate the reply.
- Mike

Max. heap size - possibility to set in jar file ?

Hi everybody,
my first question ;-)
I used java webstart for a while to roll out my software to 2 other colleagues. There was a possibility to set the starting and maximum heap size via the jnlp file. Recently I switched my "deployment process" to a simple jar file. I looked through the jar docs and googled a bit until I found this in the [bug database|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4682105]
and especially:
When jar file is read the maximum heap size is already set.
It is not feasible to introduce this feature.
So the only way to do this is using a script ?
Thanks in advance and enjoy your day,
Michael

Thanks for your quick and economic response.
Another way would be to use a tool like Launch4j which builds an exe file. Until now I have not been a friend of exe files for java programs. Since my application is only used in Windows environment I will have to rethink this opinion.

How to set max-heap-size outside the jnlp file?

Due to bug_id=6631056 It may not be possible to specify max-heap-size within
the JNLP file for certain jnlp java applications.
Are there other possibilities to specify this Jvm parameter?
In the ControlPanel there is the possibility to specify Xmx for applets but not for jnlp.
I have tried to add properties like
"deployment.javaws.jre.0.args=Xmx\=128M" without success
Many thanks

Even in JNLP also you can specify the max heap size
<j2se version="1.5+" initial-heap-size="128m" max-heap-size="512m"/>
Thanks,
Suresh
[http://sureshdevi.co.in|http://sureshdevi.co.in]

Setting System-Wide Max Heap Size

We want to set the heap-size of Java-Plugin 1.5.0_14 for a company-wide rollout to a fixed size under Windows XP.
In deployment.config under C:\Winnt\Sun\Java\deployment I am giving this:
deployment.system.config=file:C:\\WINNT\\Sun\\Java\\Deployment\\deployment.properties
deployment.system.config.mandatory=true
In the respective deployment.properties I am giving
#deployment.properties
deployment.cache.max.size=50m
deployment.javapi.jre.1.5.0_14.args=-Xmx256m -Xms75m
While the cache-parameter is taking effect (visible in the Java Control Panel) there is no change in the Max Heap Size.
Any idea how this could be achieved?
Thank you
Michael

MaxHeapSize I determine with Runtime.getRuntime().maxMemory()
Setting it manually in the javacpl via -Xmx works fine but....
Problem is that we do not want each user to open his Java Control Panel and set this value manually.
May be error prone and difficult to communicate in a scenario where you have hundreds of users in different locations, countries etc.
Should be possible to set this value once installing the Java Plugin
Thank You
Michael

"Could not create the Java virtual machine." when max-heap-size is 926Mb

We received "Could not create the Java virtual machine." when the max-heap-size provided exceeded 926 Mb in XP PC. We found the below mentioned link which confirms that this is a bug
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6945136
But the problem is that the issue does not get recreated in all the XP PCs. Increasing the max heap size to greater than 926 works fine in some XP PCs.
Could there be any configuration related issues for this problem...

If you can't find any difference in your java versions or overall runtime configurations, it's quite possible that the bug doesn't have the complete picture--it might be more subtle than the conditions described. Maybe it works with certain versions of certain lower level DLLs. Maybe it has some dependency on which services are running. Maybe the order in which certain components got installed put one version of something vs. another further ahead in a CLASSPATH, LD_LIBRARY_PATH, etc. variable.
Or maybe it's as simple as you're not running the version of Java you think you are on all those boxes, as jschell suggests.
Regardless of the reason why it happens to work on some configurations, you found that it fails on some, and that failure is in fact a known bug. So it shouldn't surprise you that it fails at least sometimes, and the fact that it works sometimes has been rendered irrelevant. Unless you're doing research into the specific cause of this issue.

Strange: Mac screen menu-bar requires max-heap-size to be set.

I planned to omit the max-heap-size attribute in the line of my jnlp file
<j2se version="1.6+" max-heap-size="256m" />
The idea was that with Java 1.6 the heap size is set automatically
according to the client's RAM.
Unfortunately, the Macintosh screen menu-bar works if and only if the max-heap-size attribute is present.
It is a MacOsX=1.4 with Java1.5.
Strange, since the Mac runs Java 1.5 and I am talking about settings for 1.6.
The jnlp passed ValidateJNLP at http://mindprod.com/jgloss/jnlp.html#VALIDATION
Here is another post stating that attributes in JNLP have side effects on Mac's screen menu-bar:
http://lists.apple.com/archives/Java-dev/2008/Jul/msg00122.html
Here is my jnlp:
w3m -dump http://www.bioinformatics.org/strap/strap.jnlp
Is there an explanation for this?
Christoph

user10289576 wrote:
I would not blame Macintosh.
The error might still be in the Sun's code.Could be. But to fix the Mac VM it would require the following.
1. Find it in the Sun VM.
2. Fix it in the Sun VM.
3. Move the changes to the Mac VM...somehow.
>
If the jdk would be smaller, less redundant and clearer, then
open JDK could be possibly compiled on a Mac.
Not sure what that means since there are likely OS level calls that must be implemented in some place in the API. Which are specific to Mac.
Just as there are differences between windows/solaris/linux which Sun accounted for.
And that would be what Apple would have done to make it work on Mac. And what someone (someone who likes Mac) will need to continue to do with the public release (explusion?) which is the form that Java will have going forward.
The main thing that should be improved on a Macintosh
is to directly allow for Linux and Solaris executables such that the Linux JDK could directly work on a Mac.The main thing, again, is the Apple is no longer supporting Java on the Mac.
And Apple, not Sun and certainly not Oracle, were the ones that created the Java VM.
So the main thing at this point is that ALL future directions that Java take are dependent not on Apple but on the Macintosh community. That includes features as well as fixes.

Does the jvm allocate complete max heap size initially?

Does the JVM allocate the memory for the entire max heap size up front, or does it start with the specified minimum size and increase and grab more later if needed?
The reason this is being posted is because we have a number of jboss servers that are being run. Some don't require large heap sizes, others do. If we use the same large max heap size for all would all the memory get allocated up front, or possibly a smaller initialization portion?

I have done the test with Solaris, Linux and WinXP.
Test with -Xms512M
Have written a simple java program to which the minimum heap size was set to -Xms512m then the program was executed on Solaris and WinXP platforms. The usage of memory of the Java process was 6 MB in WinXP and 9 MB in Solaris, rather than 512 MB. The JVM is not allocating the configured minimum size of 512 MB at the start of the process execution.
Reason:
If you ask the OS for 512 MB it'll say "here it is", but pages won't actually be allocated until your app actually touches them.
If the allocation is not being made initially during the start of the process, the concept of minimum heap size is not required.
But the garbage collection log shows the minimum heap size as what was configured using -Xms option.
Test with -Xms1024M
The JVM arguments was set to : -Xms1024m -Xmx1024m, but the used memory observed using Windows perfmon was 573M.
6.524: [Full GC 6.524: [Tenured: 3081K->10565K(967936K), 0.1949291 secs] 52479K->10565K(1040512K), [Perm : 12287K->12287K(12288K)], 0.1950893 secs] Reason:
Optimization is something that the operating systems do. The JVM allocates the memory in it's address space and initializes all data structures to your -Xms. In any way that the JVM can measure, the allocation from the OS is complete. But the OS doesn't physically assign a page to the app until the first store instruction. Almost all modern OSs do this.
Hope this is helpful.

Siginficance of max heap size mentioned in configtool

Hi all,
could anyone please tell me the exact significance of
max heap size mentioned in configtool in SAP Netweaver in
1)Instance_ID
-servers general
-message servers and bootstrap
2)Dispatcher_ID
-general
-bootstrap
3)Server_ID
-general
-bootstrap
Which of these do i change to improve the performance?
I tried changing the max heap size specified in
Server_ID
-general
but i got the following error while trying to start the server in std_server0.out:
node name : server0
pid : 3452
system name : N02
system nr. : 01
started at : Tue Mar 20 21:53:37 2007
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 1912] MtxInit: -2 0 0
Error occurred during initialization of VM
Could not reserve enough space for object heap
Regards,
Namrata.

Hi,
The biggest impact to runtime performance will be adjusting the heap size of the server JVM. This is done in Server_ID->general. The JVM parameters entered here take precedence over parameters in Instance_ID->servers general. The server job by far do the most work in the Java engine and so it is very important that the JVM for the server node is tuned to handle the workload. Tuning the server JVM or even adding additional server nodes is dependent on the workload and the amount of work on the system.
Adjusting the heap for the other JVMs will have much less of an impact than adjusting the heap in the server JVM.
The dispatcher JVM heap settings may have a slight impact during runtime, but compared to the server jobs the dispatcher does relatively little work. Depending on your situation you may need to tune the dispatcher a little, but my experience has been that the default value for the dispatcher is usually sufficient.
The values for all of the bootstrap jobs may have an impact on startup time, but they will have no impact on runtime since these jobs go away once the system is up. From what I have seen the defaults values for the bootstrap jobs are sufficent.
I never adjust anything under Instance_ID, I'm not sure what these parameters are used for except for maybe default values when adding server nodes. Maybe someone out there knows.
Hope this helps.
Regards,
Kolby

How do define the limit of the max heap size?

Hi All,
I would like to know what should be the limit of the JVM max heap size.
What will happen if we will not define it?
What is the purpose of defining it from the technical point of view?
Thanks
Edited by: Anna78 on Jul 31, 2008 12:36 PM

Defining a max heap space too large can have the following effect:
If you create new objects, the VM may decide it is not worth getting rid of garbage-collectable ones, as there
is still plenty of space between the current heap size and the max allowed. The result will be that the
application will run faster and will consume more memory than it really needs.
If the heap size is too small, but still sufficient, the application will do a lot of garbage-collection and therefore
run slower. On the other hand, it will stay inside the tight space it has been allowed to use.
The speed difference may or may not be noticeable, while the difference between 256M and 512M may
or may not matter on today's computers.

Max heap size reached : out of memory

Hi All,
I have used max possible -Xmx value on a 32 bit Windows machine,
while starting oc4j from command line and the (oracle) routeserver
initialization failed.
Did anyone face this issue or has any idea on how to initialize route servlet without errors
after reaching the max -Xmx value? Should we further partition the data?
Thank you,
-J

HI
On windows we have a limitation that heap cannot be more than 2gb.
You can have 2 JVM and check if it helps.
First and foremost you need to find whether there no objects leak in the code.
Cheers
Priya

Max Heap Size?

Hi, is it possible to change the heap/stack size (Xms and Xmx options) on-the-fly
at runtime? I have a program that uses a small stack size at times, but then
sometimes will need a huge stack size. i don't want to tie up the resources of
the machine if i don't have to.
Any ideas? thanks

I have a program that uses a small stack size at times, but then sometimes will need a huge stack size.Read (carefully) up on the Thread constructor which allows for a stackSize argument.
If this doesn't sound helpful or just doesn't work, rework your algorithm to remove recursion.
In terms of maximum heap size, simply set it before you start the application - remember, this is an upper bound of heap size, not what is consumed by default.

Max heap size limits

I've been looking around for information on the max heap size limits on Sun's JVMs but can't seem to find any information. Just by testing, it seems like the max heap size for Windows 2000 can vary from 1.3G to 1.6G depending upon the machine (JDK 1.4). Does anybody know where I could find actual documentation that describes the limits for Sun's VMs on Windows (2000 and Advanced Server), Linux, and Solaris? I'm about to file this as a documentation bug against the JDK.
God bless,
-Toby Reyelts

There was an older thread in the forums that had some info on this - my quick search failed to locate it, ypu might want to spend some time looking. The basic problem is memory space fragmentation by the OS, where the OS locates items in memory and effectively constrains heap growth to the unfragmented area that the heap starts in.While there may be more "unused" memory, it's not contiguous. There is also some info in MS's MSDN data regarding this condition, with information on the various OS's. I think Linux has a similar "condition".

Is it possible to set the heap size limits in system-wide config?

Hi,
I am trying to set the JRE heap size limits (-Xms and -Xmx) by using the system-level deployment.properties file. The JRE version is 1.6 update 6.
Normally, I would have something like this in the user-level deployment.properties file:
deployment.javapi.jre.1.6.0_06.args=-Xms64M -Xmx192MHowever, when the same line is put in the system-level properties, it does not seem to have any effect. I have tried different options, also unsuccessfully:
javaplugin.vm.options=-Xms64M -Xmx192M
or
javaplugin.minHeapSize=64m
javaplugin.maxHeapSize=192mIs it not possible to address this setting via system-level properties at all? I am hoping that I will not have to resort to per-user config files.
Best regards,
Martin

Hi Michael,
thank you for your answer. I am sorry, I was unable to find the link to the message 10144001.
My ultimate goal would be setting the system level settings as opposed to settings per applet. I was unable to find any mentioning of "deployment.javapi.jre.X.X.X_XX.args" in the official documentation here: http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/properties.html
Best regards,
Martin

Max possible heap size?

Similar Messages

Maybe you are looking for