Reporting Performance Issues

For intermittent slowness, after you stop collecting data, a log file opens in the terminal window with the last 10 lines of CDS.log and a high-level summary of callstacks. It is recommended that you send the log to the Cadence support team along with your problem description or by at least writing down the names of the functions on which the most time was spent. Functions with larger and smaller extremes are of particular interest. If the time taken is higher with a small depth then it might be the cause of bottleneck.

---------------------------------------------------------------------------------

Simplified call-chains by package (>=3%):

Order Time(%)    Count   Call-chains

  1    30.6        53    IL->CPH->OA->DB->ROD->TECH->SYSTEM

  2    25.4        44    IL->CPH->OA->DB->ROD->TECH->OA

---------------------------------------------------------------------------------

High-level summary on main thread: total 173 non-idle callstacks ('*' >30%)

Depth Time(%)    Count   Function

* 1    30.6        53    OpenAccess_4::oaDataTbl::read

* 2    31.2        54    OpenAccess_4::oaDatabase::readDataTbl

* 3    54.9        95    OpenAccess_4::oaDatabase::read

where,

• Simplified call chain: Groups function calls in a callstack using software packages, such as openAccess (OA) or tech file (TECH).
• Time(%): Displays approximated percentage of time spent in each function call. Closer to reality when more callstacks are recorded.
• Depth: Calculates the average depth measured from the top of each callstack. The function with a higher time percentage and a smaller depth can be a bottleneck.

In case an application freezes, Cadence recommends that you terminate the current Virtuoso session using the Health Monitor tool instead of killing it directly. Remember to enter your problem description in the Terminate Virtuoso form before you click the Terminate Virtuoso button. The Health Monitor tool collects the output of the UNIX top command and generates a high-level summary from 10 seconds of callstacks. This information is automatically appended to the CDS.log file and copied to hangReport*.log.CDS.log. You can send the hang report to the Cadence support team in the same way as reporting a crash.

Reporting Slowness

To report slowness using the Health Monitor tool, perform the following steps:

1. In the Health Monitor form, enable Expert mode.
2. Expand the Program Execution Tracing section.
3. Choose the Open report form option.
4. Click Start Recording.
5. After recording for some time, click Stop Recording.
   The Report Slowness form appears.
6. Type the issues in the form and click OK.
   This information is appended in the slowReport*.log.CDS.log with the system information and analyzed callstacks. Use the shell environment variable CDS_ERRORLOG to customize the file name and the log directory specified in the slow report.

To avoid opening the Report Slowness form and receive callstacks only, disable the Open report form option from the Program Execution Tracing section.

Related Topics

Health Monitor Overview

Monitor by Strace Form

Health Monitor Form

Return to top