...
- Need to talk about compression. That is a big item in the performance discussion.
- As mentioned above, configure the app to store data on another disk, preferably a RAID field with fast access and big capacity. Put the database there as well. This is done in FileSystemMgt service configuration.
- Limit logging level to Error (see Logging Configuration to find out how).
- Optimize Forwarding and other DICOM communication:
- Note, that DICOM is generally an inefficient protocol. It takes quite a few handshakes to send or recieve a single study..
- Use forwarding sparingly. Every location in your forward list means an association needs to be established and data transferred for every study recieved - every forward increases the time consumption for a single recieved study exponentially.
- Configure the Move SCU Service retry intervals.
- Try not to forward to an SCP that is frequently down. This will result in many retries, consume a lot of time (and resources), and hinder other forwarding rules from smooth operation.
- Limit the number of events logged by the Audt Record Repository service (see the AuditLogger MBean Service for more information).