Last post Jun 10, 2015 04:32 PM by jwhite100
Jun 09, 2015 12:20 PM|jwhite100|LINK
I have just published my ASP.Net application using GoDaddy's shared hosting. I am using Entity Framework 6 with Web API and the application is making AJAX calls to the Web API controllers. After the application has been idle for around three to four minutes,
it takes around 26 seconds to make the AJAX calls. It is a lot faster on my development computer. Usually a few seconds, although, it can take as long as 15 seconds occasionally. Is this because of the poor performance of the hosting provider or is there
something I may have done wrong? In my research, I have seen a couple of complaints about GoDaddy database performance, so I am leaning that way. Changing the Load Balance Timeout in the connection string seemed to have no effect. If it is the host, is there
anything I could do to improve the performance? Below is the connection string. Thanks in advance for any help!
<add name="MyDBContext" providerName="System.Data.SqlClient" connectionString="Server=xxx.xxx.xx.xx; Database=TestMyDatabase; ;Load Balance Timeout=1000; User ID=xxxxxx; Password=xxxxxx; Trusted_Connection=False" />
Jun 10, 2015 01:38 AM|Edwin Guru Singh|LINK
As per your case, the given database connection string is fine. Have you tried the same db in localhost or iis & check the initial response time.
Are you using
database mirroring concept in your db ? .because If the mirroring session is paused, the client typically connects to the principal server and the downloads the partner name. However, the database is unavailable to the client until mirroring resumes.
here to get the guidelines about Improving the Quality of SQL Server Database Connections.
If still no improvement, Please contact the corresponding hosting network server administrator.
Jun 10, 2015 04:32 PM|jwhite100|LINK
I have should have made it clear before that I was using the local host and a local database when making the comparison. And after doing some more testing it is taking around 6 seconds to get an initial response on the local machine. I also tried to connect
to the production database from the local host and was getting the same long wait time.
I am not using database mirroring and I will follow your advice and try contact the hosting provider. Thanks..