Skip to main content
Skip table of contents

How to troubleshoot a slow program

CDM+ is designed to be responsive and handle large amounts of information. However, you may encounter an area that is not optimized for your particular data set, or you may have a network issue that is slowing down access to your database. In these cases, you can perform diagnostic steps to assist Suran's technical support and development teams in troubleshooting and resolving the performance problem.

Follow this guide to collect helpful data to send to support@suran.com.

Requirements

The following steps require:

  1. Access to the Utilities window in CDM+
  2. Ability to locate details about your device, and operating system
  3. OPTIONAL BUT RECOMMENDED The ability to record your screen

Determine the environment

Collect the following information:

  1. The type of internet connection (cable, fiber, DSL, etc.)
  2. The internet connection speed per your ISP
  3. The network connection of the affected device—hard-wired (ethernet) or using Wifi
  4. If all devices are experiencing this issue or just one
  5. If the issue occurs with the same device on different networks
    1. For a laptop/tablet/phone try reproducing the issue from home or a friend's home network
    2. For a desktop or any device, try using a hotspot to reproduce the issue from a cell network
  6. The program version
  7. The operating system and version of the affected device
  8. The CPU type and installed RAM or model of the affected device
  9. Any other information on what might have changed if the program previously performed well and this slowdown is new

Test the network

These steps usually apply for hosted clients, but may be insightful for a self-hosted, local connection.

  1. Go to speedtest.net
  2. Perform a test
  3. Take a screenshot of the results
  4. In CDM+, go to CDM+ About CDM+ on macOS or File About CDM+ on Windows
  5. Click the System Information tab
  6. Note your server host name or IP address

Ping your server

Use the command prompt to ping your server with the following command, replacing server  with the server you identified in System Information. Copy the results.

macOS

CODE
ping -c 5 server

Windows

CODE
ping server

Isolate a slow operation

The program may be slow in general, or there may have a specific operation that is slow. Focus on one specific operation, even if there is a general speed issue.

An operation is defined as the behavior that occurs between clicking a button/menu item/toolbar/list line/key press/etc. and when control is returned, meaning you are able to interact with the program again.

Example operations include:

  • Opening a window
  • Refreshing a report
  • Clicking a line in a results list
  • Double-clicking the program icon to open it
  • Closing a window

Note the exact operation you are performing.

Record the operation

If you can record

If possible, and if it does not slow down the computer, record this operation using screen sharing (e.g. Zoom).

  1. Open Zoom
  2. Start a meeting (if you are not already in one)
  3. Record your screen
  4. When finished, end the meeting
  5. Wait for Zoom to transcode the recording
  6. If your Zoom saves recording to the cloud, copy the link to the cloud recording
  7. If you have an mp4 file on your computer, upload it use the File Depot

Be sure to show any report setup or specific settings that might affect the operation in the screen recording.

If you cannot record

Take screenshots of any setup windows/tabs/options that development might need to reproduce your setup.

Profile the operation

Profiling will capture detailed information about the slow operation that development can use to troubleshoot the cause of the slowdown. Follow the steps below for your version of CDM+.

CDM+ 11.1 and later

  1. Go to File Utilities
  2. Select Open Method Profiler
  3. Click Run Special Function
  4. Prepare to run the slow operation (for example, configure your report but do not click Refresh)
  5. Click Start Profiling on the method profiler
  6. Perform the slow operation ONLY (for example, click Refresh on your report)
  7. Wait for control to return
  8. Click Stop Profiling on the Method Profiler
  9. Click Export to produce a file that you can sent to support
  10. Close the method profiler window

CDM+ 11.0 and earlier

  1. Go to File Utilities
  2. Select Set Logging Level
  3. Click Run Special Function
  4. Chose SQL
  5. Click OK
  6. Select Open Method Profiler
  7. Click Run Special Function
  8. Prepare to run the slow operation (for example, configure your report but do not click Refresh)
  9. Click Start Profiling on the method profiler
  10. Perform the slow operation ONLY (for example, click Refresh on your report)
  11. Wait for control to return
  12. Click Stop Profiling on the Method Profiler
  13. Click Export to produce a file that you can sent to supporte
  14. Close the method profiler window
  15. On the Utilities window click Show Application Log 
  16. Send a copy of the application log file to support

Report the slow down to support

Email the items you collected to support@suran.com:

  1. The environment details
  2. Your speed test results
  3. Your server from System Information
  4. Your ping results
  5. A description of the slow operation
  6. The method profiler results
  7. The application log (for CDM+ 11.0 and earlier)
  8. The screen recording or screenshots of your setup
  9. Your expectation for how quickly the program should behave

Support will engage the development team to troubleshoot the root cause of the slowdown and work toward a resolution.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.