ConnectR Performance
Server Requirements
The ConnectR Server software requires that a dedicated server be used to run the software. For best performance, it is recommended that the server have quick disk access, adequate processing power to convert hundreds of thousands of healthcare messages daily, and abundant RAM to minimize swap-file usage. The machine must also have a relational database management system (RDBMS), as well as the ConnectR interfaces.
Hard Disk and RAM Requirements
- The minimum disk space requirement is 20MB. However, this will vary depending on the ConnectR functions that the user accesses. (Additional disk space will be required if the user is performing Import/Export functions. In this case, an additional 100 MB of Hard Disk space is recommended).
- The minimum RAM requirement is 32MB, but this will depend on the functions that the user will be accessing. (Additional memory will be required if the user is performing Import/Export functions. In this case, an additional 96 MB of RAM is recommended).
Processing Transactions and Hard Drive Considerations
ConnectR Server utilizes a store and forward mechanism for each transaction it processes. Each transaction (that moves from one application to another through ConnectR) is temporarily stored on the hard drive of the ConnectR Server. The benefit to this is that each transaction can be accessed at anytime— and this means that errors in and with messages can be fixed and resubmitted at will. The disadvantage is the potential for requiring a vast amount of disk space.
Additional disk space is necessary if the customer site uses the auditing features of ConnectR to keep a record of transactions and user activities via the front-end.
From our experience at customer sites, we have developed an algorithm to determine the minimum disksize
requirements for ConnectR Server:
(#TPD) x (6kB) x (#DTH) + 1GB = Minimum Hard Disk Requirement
For example, a customer predicts to have 100,000 interface transactions per day, and would like to hold the audit trail for 14 days. The disk space required on the ConnectR Server will be: 100,000 x 6,000 x 14 + 1 = 9.4 GB
- TPD is the number of transactions per day expected by a customer. Each registration, scheduling, result, dictionary update will result in a transaction.
- DTH is the number of days the customer wishes to hold the audit trails on their ConnectR Server.
Memory Considerations
In addition to the ConnectR processing code, the operating system (Windows NT or Windows 2000) and MS SQL Server 2000 is loaded in RAM.
From our past experience with customers, we have developed an algorithm to determine the minimum
RAM requirement for ConnectR Server software:
(#INT) x (20M)) + (#TTE) x (100)) + .5 GB = Minimum Memory Requirement
For example, a customer predicts that they will have five ConnectR interfaces, and that they will have
1,000 rows in the Translation Tables. The minimum memory requirement will be:
(5 x 20,000,000) + ((1,000) x (100)) + 500,000,000 = 600.01 MB of RAM.
- INT is the number of interfaces that customer projects to service using ConnectR
- TTE is the number of translation table entries that a particular customer projects to need. There could be one entry per dictionary entry is the application uses translation table entries heavily.
Capacity
There isn’t a hard cap on the # of interfaces that can be installed, but at some point you will start to run out of resources on the server and will need to split all new interfaces on to another ConnectR instance.
| #Interfaces | Notes |
| 0 - 60 | No issues as long as RAM and CPU’s aren’t being pegged (i.e. under spec’d server) |
| > 60 | Need to run IDXConnectR service as a user account that is NOT running anything else on that server |
| > 75 | Probably should apply the reg fix outlined in KB article |
| 100 - 120 | Have clients running this # successfully with the changes above |
| > 120 | Uncharted waters, haven’t seen much success running this many |