1. Configuring the ODI 12C Studio
1.1 to modify the-XMS and-xmx of the ODI studio process
Ide.conf:modifying the initial heap size (-XMS), and/or maximum heap size (-XMX) of the ODI Studio Java process.
Path: "$ODI _home\jdeveloper\ide\bin\ide.conf (my path is D:\Oracle\Middleware\Oracle_Home\jdeveloper\ide\bin\ide.conf)
# Set the default memory options for the Java VM which apply to both 32 and 64-bit VM‘s.
# These values can be overridden in the user .conf file, see the comment at the top of this file.
AddVMOption -Xms128M
AddVMOption -Xmx800M
However, this file has the following paragraph:
# This configuration file is not intended to be modified by the user. Doing so
# may cause the product to become unstable or unusable. If options need to be
# modified or added, the user may do so by modifying the custom configuration files
# located in the user‘s home directory. The location of these files is dependent
# on the product name and host platform, but may be found according to the
# following guidelines:
#
# Windows Platforms:
# The location of user/product files are often configured during installation,
# but may be found in:
# %APPDATA%\<product-name>\<product-version>\product.conf
# %APPDATA%\<product-name>\<product-version>\jdev.conf
#
# Unix/Linux/Mac/Solaris:
# $HOME/.<product-name>/<product-version>/product.conf
# $HOME/.<product-name>/<product-version>/jdev.conf
#
# In particular, the directives to set the initial and maximum Java memory
# and the SetJavaHome directive to specify the JDK location can be overridden
# in that file instead of modifying this file.
#
#-----------------------------------------------------------------------------
So we're looking for%appdata%\<product-name>\<product-version>\product.conf.
My C:\Users\XQZT\AppData\Roaming\odi\1.0.0.0.0\product.conf, the initial content is as follows
Setjavahome C:\Program files\java\jdk1.7.0_67
Modify the initial heap and the maximum heap size to twice times the original
SetJavaHome C:\Program Files\Java\jdk1.7.0_67
AddVMOption -Xms256M
AddVMOption -Xmx1600M
1.2 Modifying the MaxPermSize of the ODI Studio process
"Odi.conf" file:modifying the other Java properties of the ODI Studio process.
Path: "$ODI _home\odi\studio\bin\odi.conf"
(My path is D:\Oracle\Middleware\Oracle_Home\odi\studio\bin\odi.conf)
IncludeConfFile ../../../jdeveloper/ide/bin/ide.conf
AddVMOption -Dproduct.cluster.dirs=..
AddVMOption -Doracle.fmw.dir=odi/studio/
AddVMOption -XX:MaxPermSize=256M
can modify Addvmoption-xx:maxpermsize
2. Odi_init_heap and Odi_max_heap of the proxy agent configuration
D:\Oracle\Middleware\Oracle_Home\user_projects\domains\odi_domain\bin\setODIDomainEnv.cmd (setodidomainenv.sh)
In Oracle Data Integrator 12c the odi_init_heap and Odi_max_heap parameters is located in the Setodidomainenv script file Within an ODI domain Bin directory.
Modify the content inside
Set wls_mem_args_64bit=-xms512m-xmx512m
Set wls_mem_args_32bit=-xms512m–xmx512m
------
Set mem_perm_size_64bit=-xx:permsize=128m
Set mem_perm_size_32bit=-xx:permsize=128m
Description
The JVM primarily manages two types of memory: heap and non-heap.
The code for the method area, internal processing or optimization of the JVM (such as the JIT-compiled code cache), each class structure (such as running a constant pool, field, and method data), and methods and construction methods are in non-heap memory.
A heap is a run-time data region where all class instances and arrays of memory are allocated.
-xms128m JVM Initial allocation of heap memory
-XMX512M JVM Maximum allowable allocated heap memory, on demand
-xx:permsize=64m JVM Initial allocation of non-heap memory
-xx:maxpermsize=128m JVM Maximum allowable allocated non-heap memory, on demand
Reference:
ODI 12C Studio running slowly
Http://www.oracle.com/us/products/middleware/data-integration/odi-performance-guide-wp-2147067.pdf
Xms Xmx permsize maxpermsize Difference
Java Foundation---->java Virtual machine Run Environment data region description
Troubleshoot the ODI 12C Studio slow run problem