|
Hi Everyone, we are using the sql 2005 for my application. One of my client reported like when ever he typed the URL like http:google.in(my application url)the page is opening very fast when he tried to login its taking more time.so he is asking to resolve this. So please suggest what was the actual cause?What are all the things i need to check? Thanks in advance..
(comments are locked)
|
|
I'm confused. You mean that your client is able to browse the internet but is having trouble connecting to your app? Is your app local to the client or is it also on the internet? If your app is on the internet and the client is browsing to it, then there are four factors that will affect them 1) Their connection to the internet 2) General internet performance 3) Distance to your site 4) Your site's connection to the internet. You can't do anything about 1 or 2 and it sounds like they're not the issue. As to 3 and the general issue of latency, how far away is the client from your machine? Are you on opposite sides of the planet? That will cause rather severe performance issues. The way around it is to put up mirror sites in various locations in order to reduce latency, or, at least, make your app as non-chatty (reduce round trips) as possible. To address 4, you need to look to your machines. Are you having issues? What's the turnaround time locally? Are there other problems? You haven't provided enough information for me to make a guess on this one. Thanks for reply.. My application is working in internet yes the users and servers are opposite sides but only few users raising the issue..
Jun 01 '10 at 09:03 AM
vijay 2
Network latency is just a huge issue. There's no magic bullet. Everyone compares to google, but google has machines all around the planet so that no one has to travel far to get the signal. Just remember, 18 inches is about how far an electron travels in a millisecond. That's a physical limitation on speed. You have to reduce volume, reduce signal or reduce distance, or all three.
Jun 01 '10 at 10:46 AM
Grant Fritchey ♦♦
(comments are locked)
|
|
Hi, That is something to do with your database connection when users try to log in. You can use sql profiler to trace the store procedure to check which part taking too long to process. Thanks.
(comments are locked)
|

