...
Here are some tips, and general directions for tuning the dcm4chee system.
| Warning | ||
|---|---|---|
| ||
Always make a complete backup before modifying the dcm4chee deployment, and test thoroughly before using in production! |
Server(s)
If you want to install everything (database and dcm4chee) on one machine, it is good to have a lot of memory and processing power to satisfy the needs of the system. Volume, types of images, number of concurrent users (DICOM, HL7, and human), and throughput requirements all play into the hardware decision. In general it is a good idea to run the database and the dcm4chee system on separate machines in a production environment. There will be network overhead between the two servers, but the benefit lies in the dedication of appropriate memory, processors, and storage to each application (dcm4chee and database).
...
If you want to be sure you're getting maximum performance from the application server, you might have to dig into JBoss performance tunig.. One good step however is to give the server enough memory - see the Installation notes to see how. To find out more about JBoss Tuning tuning see JBossASTuningSliming JBoss wiki page on the JBoss wikitopic. JBoss tuning (like database tuning) is an endeavor unto itself, and the JBoss website, wiki, and forums are the places to go for that type of information.
...