IBM Support

Java processes accessing the memory upon executing a performance test

Question & Answer


Which are the Java processes accessing the memory upon executing a performance test under IBM Rational Performance Tester (RPT)?


Understanding of the Java processes involved while working with RPT will help fine tune the scalability of the script execution in any given environment.


There are 2 types of Java processes involved while working with RPT.

  1. Javaw: This process represents the Eclipse workbench. This will be present as soon as you log into RPT and will stay active until you exit the workbench. The heap size is configurable using the Eclipse.ini. You can allocate up to 1200 MB (assuming you have enough free memory available on your system). This will control how the JVMs garbage collection is invoked. The JVMs heap, stores all objects created by an executing Java program. Objects are created by Java's New operator, and memory for new objects is allocated on the heap at run time. Garbage collection process automatically frees objects that are no longer referenced by the program (based on the heap size you set). You can monitor the actual memory being allocated by viewing the javaw process from task manager.

  2. Java: This process will kick off as soon as you execute a test or schedule within the workbench. The memory consumption is based on a number of factors which include the total number of Virtual Testers, the content size of the recorded test, looping, and custom code (Among other factors). General suggestion is having at least 2 to 3 MB of RAM available for each Virtual Tester being run. This process will be active for the length of the run. As soon as the run is complete the process will end and the memory will be released. You can allocate the amount of memory for each agent controller.

[{"Product":{"code":"SSMMM5","label":"Rational Performance Tester"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"General Information","Platform":[{"code":"PF033","label":"Windows"}],"Version":";;8.3;;;;;;8.2.1","Edition":""}]

Document Information

Modified date:
16 June 2018