> > Colleagues, > > What frightens me is that I've seen up to seven [7] diallers on a small > server. I've had recent contact with a practice with 5, all working > somehow, believe it or not. All the usual suspects mentioned in the > discussion were present. For how long is the question, and what happens > when one or more of them break? What else will come down? > > To me this complexity and overhead is the real problem.
Hi Greg, When you say 7, do you mean running concurrently or simply installed? The downloaders I've come across all have "run-connect-download-quit" functionality, so they only steal resources while running. Typically this would be only for a minute per program every two hours. I tend to avoid if possible the downloaders built in scheduling that obviously requires CPU+RAM resources to keep active. Cron, LaunchD or the built in Windows scheduler is surely a better option than having X number of clients waiting around in RAM? Are there downloaders out there that don't allow for this? None of this is in contravention of the two decent points raised earlier: 1. Downloaders should be installed on client machines or a "sub-server". 2. A universal downloader would be ideal. Also... I've only got a working knowledge of Genie, so wonder if other clinical packages allow the client to insert the path result into the database from the client (with the result residing on the client HD, not the server)? This scenario means that there is no reliance on the client operating systems connection to the server (mapped drives, UNC pathways etc). Downside is that it is only practical for one computer to import the path, however this tends to be a bigger limitation on paper than in reality. Regards, Simon _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
