Search

Performance Tuning Guide

Performance Tuning Guide

10.3

Back Next

Recommendations for the Hub Console Optimization

Recommendations for the Hub Console Optimization

The Hub Console parameters can be optimized for better performance.

The following table lists the recommendations for the Hub Console optimization:

Parameter	Recommended Setting	Description
Hub Console - Java (JNLP) Heap Size	Initial Heap Size: 128m (Default) Maximum Heap Size: 512m (Default).	jnlp.initial-heap-size , jnlp.max-heap-size This property is found in the cmxserver.properties file. If the client box, where the Hub Console is launched, can handle more Java memory, this value can be increased to add more memory to the Hub Console. Note that this memory is completely different from the JVM memory of the application server which is the server side memory.
Client Java Version (JRE)	As specified in the Product Availability Matrix (PAM).	Ensure that the client Java version is as specified in the PAM document for the product. It is not required for the Hub Console to pick the latest JRE that the client box has. The JRE version selected depends on the PATH variable. To ensure that the Hub Console uses the correct JRE, temporarily enable the console log as listed in the Informatica Knowledge Base article. When enabled, the next launch of Hub Console opens a Java console window where you can see the used JRE version in the top of the console.
Console log	Disable (Default).	Disable the logging by launching the javaws -viewer option on the client box in the run command. In the javaws window, go to Java Control Panel in the Advanced tab and perform the following steps: Clear ‘Enable tracing’ and ‘Enable logging’ options in the Debugging section. Check ‘Hide Console’ option in the Java Console section.
High Data Volume	See the parameter "High Volume of Data in C_REPOS_TABLES with historical data" in Database - General Recommendation Section.	Having huge number of records in the tables listed in the referenced section might cause multiple issues on Hub console. The following lists are the issues that might be include: batch groups screen loads too slowly. base object record is saved too slowly. cleanse function is saved too slowly.
Network latency	Good network connection.	Hub Console communicates with the Hub Server (application server) frequently. Therefore, the Hub Console must process a considerable amount of data to and from the Hub Server. Have good network connection between the client box and the application server.

For more information, search the

Informatica Knowledge Base

for article numbers 310913 and 139923.

Recommendations

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.