We have been speed testing recently, due to reported slowness in the Centricity App. We realize that over the years, the App has become more complex with MU, PQRS, CVS, CCDA, etc.
We were wondering if anyone else tests their App in regards to Logging into Centricity, opening an encounter, displaying a scanned document, etc. If anyone else is currently doing this, would you be willing to share your recorded times ?
Thank you.
John Mazurowski
[email protected]
Open first chart of the day: 19.73 seconds
Next chart: 1.86 seconds
Start initial office visit: 5.06 seconds
Start next office visit: 3.66
Running under terminal services, Windows 2008, CPS 12.0.12. We have been doing a lot of work to improve performance. We're not there yet, but we have come a long way.
Steve
Steve,
Out of curiosity, when you say "open the first chart of the day" are you including the timing for double Clicking the CPS icon and entering the username, password and location of care?
Thanks,
Mike
No I am not. This is post login to CPS - just the time to open the first chart.
Steve
We have Fat Clients.
1st Chart of Day: ~ 7 seconds
Next chart: between 1 and 2 seconds.
Starting a new office visit: ~ 2.5 seconds
Big Disclaimer: There have been times in the past that these numbers have all of a sudden been much longer. When that occurs it is like trying to find a needle in the haystack as to why. The most recent episode was just a few weeks ago after apparently some Microsoft Windows updates on the servers (suspecting a Dot Net update) caused some users extreme delays going from one chart to another (in some cases taking 60 seconds or more). After the server updates about 10-12 of our 50 users were having CPS chart speed issues. Turns out those users PC's had not installed the latest Windows Updates. Once we updated their Windows normalcy to opening CPS charts returned.
would you be willing to share a list of performance enhancements or tweaks that might speed up performance ??
anything from hardware improvements to browser settings would be helpful.
CPS 12.0 .12 here DB server 32gb ram, JBOSS server 32 gb ram
fat clients and thin clients
RDP windows 2008r2
chart opens on TS can take 20-60 seconds in mid day. Problems since 12.0.11
Any list of things to check would be helpful
GE has not been helpful at all.
Thanks
JJC
We have tested fat clients and they are much faster, but with my small staff and multiple sites we just would not be able to handle it - therefor terminal services. By the way, our testing of 12.2 showed a large performance improvement in a terminal services environment - but we are waiting for a 12.2 patch to fix a problem for our providers. I think we have about 130-150 concurrent users. VMWare environment.
1 appserver - 32 GB memory 6 CPU - 2008 R2
dataserver - 64 GB memory 8 CPU - 2008 R@ Datacenter - SQL Server 2012. Disks 64K Cluster size. TempDB on it's own drive, CPS database logs on their own drive. This weekend we will be changing CPS database to simple recovery mode, moving backups to another drive, and moving the rest of the log files off the data drive. Apparently we also have some missing indexes which I will be creating.
We have been working with GE, but we had to apply a lot of pressure to get help.
You can reduce load times with SSD drives on fat clients. It makes a noticeable difference. For me it was about a 50 percent improvement. There are a lot of SANs today which can be configured with SSD as well. Obviously it is a higher cost but makes a difference for your TS servers.
I wonder how much the cloud version of CPS will help in this respect.