You can improve server response time by reducing the size of the HTTP response. You can improve server response times by reducing the size of the HTTP response. If you choose to implement this practice, understand that the server does more work to compress files which might impact the scalability of the server under heavy loads.

To compress files that are sent to client by using the Oracle WebLogic Server, refer to the Enabling GZIP Compression for Web Applications section in the Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server Guide.

From WebLogic Administration Console, select the Domain Name in which Convergence is deployed and modify the attributes such as GzipCompressionEnabled, GzipCompressionMinCompressionContentLength, GzipCompressionContentType in the Web Applications tab.

You can configure enhancing browser caching of static files for Oracle WebLogic Server in Oracle HTTP Server.

See the mod_expires option in Apache HTTP Server and Third-party Modules in Oracle HTTP Server at: Understanding Oracle HTTP Server Modules.

For tuning JVM heap size on Oracle WebLogic Server Administration Console, see Oracle Fusion Middleware Tuning Performance of Oracle WebLogic Server Guide.

Generally, set max heap size as large as possible given the available memory on your machine. (Setting the min equal to the max improves JVM efficiency.) Total memory used is equal to the (JVM native heap space) + (Java Heap) + (Permanent Generation space). Reserve space for the operating system and any other applications running on the machine too. Don't forget to reserve memory for the OS and avoid memory swapping at all costs.

For example, you can set the heap size options to:

<jvm-options>-Xms3g -Xmx3g</jvm-options>

For more information on setting heap size options, see Oracle Fusion Middleware Administering Server Startup and Shutdown for Oracle WebLogic Server Guide.

You can update the startManagedWebLogic script with the required Java Heap Size in JAVA_OPTIONS. For example: JAVA_OPTIONS="-Xms3g -Xmx3g" ${JAVA_OPTIONS}.

See Starting and Stopping Servers section in the Administering Server Startup and Shutdown for Oracle WebLogic Server Guide.

To increase the stability and predictability of the heap size and the ratios of its configuration, you can explicitly set the following parameters. Oracle WebLogic Server with Java 8, the following GC options may get better results:

• -XX:+UseG1GC: Use the Garbage First (G1) Collector.

• -XX:MinHeapFreeRatio=10: Minimum percentage of heap free after GC to avoid expansion.

• -XX:MaxHeapFreeRatio=50: Maximum percentage of heap free after GC to avoid shrinking.

• -XX:NewRatio=1: Optimize the Young Generation Size. Using a ratio (as opposed to setting a numerical size with NewSize) allows for the maximum possible young generation size relative to the overall heap, irrespective of your MaxHeap size.

  For more information about the G1 GC algorithm, see the following Oracle web site:

  http://www.oracle.com/technetwork/tutorials/tutorials-1876574.html

  See the discussion about Java garbage collection settings on the Oracle Technology Network:

  http://www.oracle.com/technetwork/java/javase/tech/g1-intro-jsp-135488.html

Tests show that most of the objects created for Convergence are short-lived, thus benefiting from a larger young generation size.

The NewRatio means {New:Old}. So, when NewRatio=1, then new:old = 1:1. Therefore, the young generation size = 1/2 of the total Java heap. The young generation size can never be larger than half the overall heap because - in the worst case - all the young generation space could be promoted to the old generation. Therefore, the old generation must be at least as large as the young generation size.

For more information about the NewRatio option, see the following Oracle web site:

http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html

Monitor your own heap usage with JConsole. See "Monitoring Convergence" for more information.