Frequently Asked Questions
How to improve the performance and stability of Perennity DICOM
Last Updated 9 years ago
There are several ways to improve the performance (and stability) of Perennity DICOM, as listed hereunder:
- Use a dedicated PC for Perennity DICOM and the autoloader software. Make sure to only run essential software on it.
Configuration guidelines:
- CPU Intel i5 or equivalent
- minimum 8GB of RAM, add more if you're working with large data sets
- minimum 2 hard disks, at least one of them being an SSD
- If you install an antivirus program, exclude the Perennity data directories (storage, buffer) and the Rimage system folder from real-time scanning. Unfortunately we cannot provide instructions for each antivirus solution in the market. Test temporarily deactivating the antivirus software if you suspect it to be overly active.
- Use SSD disks instead of regular magnetic HDD disks: this may be the most important performance and stability improvement measure you can take. Either use only SSDs or configure the system to use at least SSD for the Perennity Server buffer folder and the database (especially if the throughput is very high with large numbers of images). We have written procedures for moving these folders.
- Use multiple HDDs and distribute the workload (storage folder, Server buffer folder, Burner buffer folder, imaging folder, database)
- Move the database folder to a dedicated HDD (or partition), preferable SSD: when studies with a large number of images are sent, Perennity has to open the header of each image to process the metadata. This also intensifies the access to the database.
- Do not create thumbnails: check if the thumbnails are essential for the customer and deselect the option to create them if the customer doesn't need them.
- Allocate more memory to the Server Java process (typical warning message "image is already being stored" may be solved in this way). Make sure your system has enough physical memory installed (at least 8GB, preferably more).
To move the database folder: stop the Perennity services (incl. database), edit the my.ini file to reconfigure the database path, copy the database folder to the new path, restart the services (database first).
To move the Server buffer folder: http://www.perennitysoft.com/support/kb/faq.php?id=72
- Use a dedicated PC for Perennity DICOM and the autoloader software. Make sure to only run essential software on it.
Configuration guidelines:
- CPU Intel i5 or equivalent
- minimum 8GB of RAM, add more if you're working with large data sets
- minimum 2 hard disks, at least one of them being an SSD
- If you install an antivirus program, exclude the Perennity data directories (storage, buffer) and the Rimage system folder from real-time scanning. Unfortunately we cannot provide instructions for each antivirus solution in the market. Test temporarily deactivating the antivirus software if you suspect it to be overly active.
- Use SSD disks instead of regular magnetic HDD disks: this may be the most important performance and stability improvement measure you can take. Either use only SSDs or configure the system to use at least SSD for the Perennity Server buffer folder and the database (especially if the throughput is very high with large numbers of images). We have written procedures for moving these folders.
- Use multiple HDDs and distribute the workload (storage folder, Server buffer folder, Burner buffer folder, imaging folder, database)
- Move the database folder to a dedicated HDD (or partition), preferable SSD: when studies with a large number of images are sent, Perennity has to open the header of each image to process the metadata. This also intensifies the access to the database.
- Do not create thumbnails: check if the thumbnails are essential for the customer and deselect the option to create them if the customer doesn't need them.
- Allocate more memory to the Server Java process (typical warning message "image is already being stored" may be solved in this way). Make sure your system has enough physical memory installed (at least 8GB, preferably more).
To move the database folder: stop the Perennity services (incl. database), edit the my.ini file to reconfigure the database path, copy the database folder to the new path, restart the services (database first).
To move the Server buffer folder: http://www.perennitysoft.com/support/kb/faq.php?id=72