Troubleshooting questions to ask when Compass appears to be running slowly
- Is logging turned on any Compass Source/Destination or is the global log level on the Compass System tab set to a level higher than ‘Terse’ ? If it is turned on anywhere, trying turning it off or to Terse and see if that fixes the problem.
- How much memory is available to Compass?
- How much free disk space is there?
- Approximately how many studies are sent to Compass per day?
- Do you have any Compass Destinations configured as ‘Immediate Mode?’ That feature can be accessed at the top of the right-hand column of the Destination configuration tab.
- What is the total number of jobs sitting in Compass including Failed and Sent jobs?
- What is the Sent jobs purge delay set to on the Compass System tab?
- Is Compass running on a virtual machine (VM)? If so, are there multiple snapshots?
- Review settings for concurrent associations:
- How many concurrent inbound associations are there? (This is configurable on a per-Source as well as System-wide setting).
- How many concurrent outbound associations are there? (This is configurable on a per-Destination as well as System-wide setting).
- One or both of these values may be too high.
- Is Compass changing the transfer syntax?
- Many concurrent associations, usually with large images, that are changing transfer syntaxes can bog Compass down.
- Configure Compass to either not change the transfer syntax (if possible), or lower the concurrent association count(s) (see “Review settings for concurrent associations” above).
- What is the refresh rate set to on the main Jobs table? Set this value to a less frequent value.