Resolution:
Description:
============
During design time, while using Designer-&gtTester to test our BW process, it runs very slow.

Following suggestions or troubleshooting tips may help resolve the issue:

Are you seeing this issue after keeping the designer running for long time?
If yes, then try the Suggestion 1 below.

Have you tried to increase the Heap size in designer.tra and still seeing the issue?
Try to set -Xms and -Xmx as in Suggestion 2 and see if that improves the situation.

Suggestions:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
1.

As designer is a Java application, closing and reopening the designer would be a good idea to initiate the garbage collection instead of keeping the designer open for days together.

As the designer has multiple palettes involved,  each resource will take certain  amount of memory and only while closing the designer it will do garbage collection. If you keep the designer open for days together without closing it , it is possible that designer is using up the memory and hence this happens. You can probably apply the java tuning parameters to do GC at certain intervals but  then it would be a good idea to close the designer and reopen the project once in a while.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

2.
You can increase the tibco.env.HEAP_SIZE in designer.tra and see whether that improves the situation  or you can add the  below tuning parameters say:-

Say your heap size is set to 512M and you add the below in designer.tra.

java.extended.properties=-Xms512m -Xmx512m As this will probably have better performance because the heap won't be growing.

And the gc can be smarter about  gc cycles since  it knows that the max memory its going to get is exactly the same as it  already has.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

3.
You can try to use this engine property:
EnableMemorySavingMode or EnableMemorySavingMode.&ltprocessName>

Memory saving mode can reduce the memory used by actively running process instances as well as potentially improve the performance of checkpoints. By default, memory saving mode is disabled, but you can enable garbage collection on specific process instances by setting the EnableMemorySavingMode.&ltprocessName> property to true. You can enable memory saving mode for all process instances by setting the EnableMemorySavingMode property to true.

If you want to set the engine property for designer you can create a file properties.cfg and put it under DESIGNER_HOME (say C:\tibco\designer\5.3) and add the engine property above in this file.

If you want to set this property for deployed application then set the above property in bwengine.xml under BW_HOME\lib\com\tibco\deployment and change tje EnableMemorySavingMode value
to true and this property will be passed on to your deployed application .tra file.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
4.
If your issue is say the you start the first job in Tester it runs fast and as you run many jobs it get slower and slower the memory consumption is high then Yes, this is the expected behaviour as designer needs to remember the job data for the user to revisit the completed jobs. Hence if the user is done with  revisiting the completed jobs in TESTER window then he can choose the completed job and close the job by clicking on X icon in Tester window and see  if that improves the situation.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
5.
Check if any Corruption in monitor screen refresh rate setup & video driver. Its possible that  designer screen was not refreshing properly and was running slow.After reinstalling  the Video driver its worked fine for one user.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
6.
If none of the above suggestion helped, maybe cleaning up the Designer profile file might help. Try to back up the C:\Document and Settings\&ltloggeduser>\.TIBCO directory and then delete the .TIBCO directory. You will lose the preferences such as alias and view layout etc  if you have added any customization in designer. Designer profile will be created the first time you bring up designer if it does not exist.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>


Environment:
============
o Windows
o BW 5.x or later

Designer Tester, to test the process takes way too long? Why?