on 09-15-2010 9:56 PM
Hi all,
One question, I'm checking note 723909 and it talks about Heap size.
My doubt, in Java config tool I have the tree in the side and when I click in the instance. there are three tabs.
In Message server and Bootstrap there is a field above Java parameters that says, max heap size (in MB), then 1024.
In the next tab, Servers General and in max heap size (in MB) I have 4048.
Is this the heap size defined on point 2.1 of the note?
Quoting:
"For 64 bit platforms (that means not only your OS but also your JDK supports 64 bit) we recommend using 2GB: -Xmx2048m -Xms2048m"
What is the value to put there? On server and message?
I have 16Gb in a 64 bit win server. What do you recomend?
Another question, what is "add server" button? It creates another node to process requests? Is it necessary to use more RAM? Because I'm seeing I have plenty of RAM but it is not used... What is necessary to create a new server?
By the way, in the parameters I have in servers general for this (one and only) instance is:
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
-verbose:gc
-Xmx2048m
-Xms2048m
-Djco.jarm=1
-XX:PermSize=1024m
-XX:MaxPermSize=1024m
-XX:NewSize=320m
-XX:MaxNewSize=320m
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-XX:+PrintGCTimeStamps
-XX:+UseTLAB
-XX:SoftRefLRUPolicyMSPerMB=1
-Dsun.io.useCanonCaches=false
-Djava.awt.headless=true
-Xss2m
-XX:+UseParNewGC
-XX:CompilerThreadStackSize=4096
What can I do to improve the processing and memory usage? I have 16gb and only 4 GB is used in total (VM included!)
Note: I've already checked on the portal monitor that it only has 1024Mg avaialble... How to increase this value?
Hi Pedro
My doubt, in Java config tool I have the tree in the side and when I click in the instance. there are three tabs.
In Message server and Bootstrap there is a field above Java parameters that says, max heap size (in MB), then 1024.
In the next tab, Servers General and in max heap size (in MB) I have 4048.
==> If you select the instance_IDxxxx, then what you are seeing is the instance level setting. but what is really effecting isn't here.
Please expand the "instance_IDxxxx", and select the "server_IDxxxx", then you will also see the following tabs:
General, Bootstrap, Log configuration, Debug.
Please adjust the parameter under "General"
Is this the heap size defined on point 2.1 of the note?
Quoting:
"For 64 bit platforms (that means not only your OS but also your JDK supports 64 bit) we recommend using 2GB: -Xmx2048m -Xms2048m"
What is the value to put there? On server and message?
I have 16Gb in a 64 bit win server. What do you recomend?
===> On your system, the recommended value is 2048M for the server's max and min heapsize, i,e -Xms2048M and -Xms2048M, also as you have
16GM RAM, so you can add at least one more server node, please select the menu "Server -> Add Server" from the configtool.
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
-verbose:gc
-Xmx2048m
-Xms2048m
-Djco.jarm=1
-XX:PermSize=1024m
-XX:MaxPermSize=1024m
-XX:NewSize=320m
-XX:MaxNewSize=320m
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-XX:+PrintGCTimeStamps
-XX:+UseTLAB
-XX:SoftRefLRUPolicyMSPerMB=1
-Dsun.io.useCanonCaches=false
-Djava.awt.headless=true
-Xss2m
-XX:+UseParNewGC
-XX:CompilerThreadStackSize=4096
What can I do to improve the processing and memory usage? I have 16gb and only 4 GB is used in total (VM included!)
Note: I've already checked on the portal monitor that it only has 1024Mg avaialble... How to increase this val
====> Finally among your parameters, the 1GB for Permsize isn't necessary, you can decrease this to 512M which should be enough.
Best Regards,
Thunder
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
First of all, thank you very much!
First, and to help others, I have a 64 bit 2003 win server with 16Gb of RAM.
After reading all topic I've defined the following for the servers (general):
Max Heap Size (in MB): 2046
Java Parameters:
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-verbose:gc
-Xmx2048m
-Xms2048m
-Djco.jarm=1
-XX:PermSize=512m
-XX:MaxPermSize=512m
-XX:NewSize=341m
-XX:MaxNewSize=341m
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-XX:+PrintGCTimeStamps
-XX:+UseTLAB
-XX:SoftRefLRUPolicyMSPerMB=1
-Dsun.io.useCanonCaches=false
-Djava.awt.headless=true
-Xss2m
-XX:+UseParNewGC
-XX:CompilerThreadStackSize=4096
-XX:+PrintGCDetails
-XX:+HandlePromotionFailure
-XX:SoftRefLRUPolicyMSPerMB=1
-XX:ReservedCodeCacheSize=64M
-XX:CodeCacheMinimumFreeSpace=2M
*********************************
BOOTSTRAP of servers:
Max Heap Size : 1024
Java Parameters:
-Djco.jarm=1
**********************************
For dispatcher
Max Heap Size (in MB): 256
Java Parameters:
-XX:NewSize=57M
-XX:MaxNewSize=57M
-Xms170M
-XX:+DisableExplicitGC
-verbose:gc
-Xloggc:GC.log
-Djava.security.policy=.\java.policy
-Djava.security.egd=file:/dev/urandom
-Djco.jarm=1
Regarding Bootstrap the 1024 heap (max) size is ok?
Once again thank you!
Hi,
If you are facing performance problem on the portal then you can increase the Heap size from 2048 MB to higher value. Initially it should be 2048 MB but you can increase it further depends upon your usage.
With Add server button, you can add more server nodes so that more number of threads are available. This you can do if load on portal is more and you can calculate maximum number of server nodes that you can add according to RAM you have. You check this formula in SAP note 723909.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pedro,
Max Heap size for 64 Bit machines recommended value is 2GB. So Please correct the parameter.If needed You can increase the parameter.
In the same way , Perm size is also recommended as
For 7.0 on 64 bit: -XX:MaxPermSize=512m -XX:PermSize=512m
Please tune the below parameters as stated above
XX:PermSize=512m
-XX:MaxPermSize=512m
Once You see the performance, You can add one more server no
Instead of increasing heap size, it is always recommended to increase the server node. So when you have sufficient memory you can go ahead and increase the server nodes.But as per the note, the server node memory consumption should fully fit into Memory.There should not be any paging. So in an average for heavy load applications (if 400 threads in an avg then ) you have to consider 3GB for each server node.
So You can go ahead and add one more server node as You have sufficient RAM with you.
Hope This will help.
Thanks,
Jagadish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.