September 26, 2013 at 12:32 pm
Our database is physically located on the East Coast, we have a COTS product were our users uses it to read, open modify records in the database as well as run reports. Our West Coast users complains how slow the application takes to respond. What can be done to help easy their pain when using the COTS application. I guess because they are on the west coast it’s going to be slow and I’m talking 20-40 seconds slow.
September 27, 2013 at 9:36 am
Hi,
We had a similar experience with one of the CRMs. We has slow long distance performance. The reason was that this application is server-performance centric - instead of issuing a big query with joins that loads the server, it issues a number of smaller queries and it generates a lot of round trips. So the server performance is good but the network latency due to multiple roundtrips makes the user interface slow. This is a client server application (application 1) . We sometimes have a similar problem with one of our web application (application 2).
The fix in our case was to install an Application 1 client on a terminal server on the East Coast and let the users to use Remote Desktop to this terminal server. The end users verified that thier performance problem has been solved. The Application 2 users log in to this terminal server too and use web browser on the terminal server to run the application 2.
Yelena
Regards,Yelena Varsha
September 27, 2013 at 12:39 pm
Interesting, thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply