Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Optimal Trace is running slow and using a lot of memory

Optimal Trace is running slow and using a lot of memory

Problem:

Optimal Trace is running slow and using a lot of memory. What can I do?

Resolution:

Optimal Trace is designed to be highly scalable and preferment however there are a number of considerations that may be a factor if high memory amounts are being used.

If you do observe a noticeable slowdown in performance there are a number of things you should check for:

1. Each Optimal Trace project carries around a file called '.ctl_docgen'.

This file is used for document updates and can consume a big amount of memory especially on startup. If left over a period of time where there are frequent changes to the project this could grow to a large size & become a problem. (this file contains the change events required to perform an update).

You are safe to delete this file if you don't do document updates (generation & reversal is fine and they do not use this file). Most users in our experience can safely delete this as perhaps about 20% are doing updates. If you delete the file, future updates can proceed as normal as the file is recreated when you start making changes again. This file is stored adjacent to file based projects. Look at 'Default Directories' in the 'General Options' for this location.

2. Memory allocation. You can increase the amount of initial memory allocated to the Optimal Trace Enterprise client or server or Optimal Trace Professional.

Increase the default heap size option (-Xmx500M) in the Optimal Trace Enterprise.lap file. This file is located in the following folder: INSTALL_DIR\Program Files\Micro Focus\Optimal Trace\Optimal Trace Enterprise Edition. The amount of increase in the heap size is dependent on your environment's memory capacity.

3. If you are doing very frequent copy/paste from external documents pdf, word etc. this can also bloat the log files or project, so check the size of the project. Optimal Trace offline projects are XML formatted and should not be large. Even complex projects are reasonably lightweight.

Old KB# 10324

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 17:40
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.