Gordon,
>On my machine it takes less than 5 seconds. When I tested the web application on the clients server, it was also less than 5 seconds. The user is accessing the system in a place called Westlock, Alberta (rural), where the system resides in Edmonton, Alberta (urban). Westlock is about 50 minute drive NW of Edmonton. The system will eventually reside in Westlock, but will be accessed across Northern Alberta. How can I make that web page perform faster or persist it's state on the client's machine and only have the data behind it refresh? Or does the page always have to come from the server? I see other applications, such as Universal Thread, performing very fast in comparison. I must be over looking something.
I don't have any stock answers on making the application faster (although you do want to make sure you have debugging turned off). Here's an article to check out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenetchapt06.aspAnd here's an article on performance monitoring, which may help you determine where the bottlenecks are:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/monitor_perf.aspRegards,
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com