Updated: Sep 25, 2018
by David Hallberg
We all know the top three priorities realtors repeat to new home buyers: “location, location, location.” Those of you working with your hospital’s IT infrastructure might similarly be able to sum up the top three desires of clinicians and administrators with one critical word: “speed, speed, speed.”
Last week I began our triage into systems operating “slow, slower, slowest.” We examined Millennium to identify the services that are backing up and causing the greatest slowdown for clinical and business users. Then I outlined the first treatment of opening up more instances to alleviate the backlog on problem servers. Unfortunately, this basic treatment will not cure every backlogged queue. So this week we will need a more radical intervention. We will examine the Shared Service Proxies (SSPs) associated with the backlogged instances and the creation process for dedicated SSPs.
The SSP is Millennium’s proprietary middleware. It’s the pipe that connects the PC or Citrix servers to Millennium’s back end. By increasing the middleware throughput, you will eliminate your current bottleneck and take users in the production domain one step closer to consistently reliable Millennium responsiveness. Best of all, you can make these corrections through your normal change control processes without any third-party support.
To continue to the step-by-step details for determining the SSP associated with your slowdown and creating a dedicated SSP, click here.