I'm just learning MVC2 for a job and I decided to rework a site that is a work in progress using it. Performance locally seems great, actually better than web forms. On wnhost is a different story. the domain is fire-cam.org and currently you can click members, then click Jerry Stankovich and that is the only complete page minus some minor layout and styling issues. The time it takes to see the page seems really long to me. The images are pulled down from a webservice and are not compressed properly nor is there any sort of loading indicator at the moment, but since that call doesn't occur until the page is rendered, it's not what is slowing down the request. Even the Members link and home page seem to be slow. Any tips or tricks would be helpful. I don't want to go to MVC 3 because the job requires 2, so that is currently out of the question. The only thing that MAY be slowing it down is that the Database isn't a Winhost one just yet, but it wasn't in the past and there were no issues. I should note that this started off as a standard vs 2010 mvc2 project. The only routing change I made was to ignore .svc files. Thanks in advance.
So to be clear, you have the web site on Winhost server, but the database exist outside of Winhost network/services. Just where is the database at? You said you have a web service, is that web service uploaded to the Winhost web servers or does it also exist outside of the Winhost network?
The db is still on my server here until i finish it. The webservice sits with the site , it's just for ajax calls. The home page does not hit the database at all and as you can see it's bare right now. I may move it over in a bit because I think i'm done for the most part. I know that can be the slow down for the pages that do pull data. Also, after hitting the site just now, performance seems much more in line with what I expect. I did make sure the browser cache was clean, so maybe it was just a brief slow time. Are there any special tricks to optimize an MVC site though?
Do you have a specific URL we can look at? And if there is a specific page that is slower than the others let us know which one or give us instructions on how to replicate the slowness on our end.
other than the main index page, nothing that is worth it at the moment. I'll finish up a few more pages and move the db and see what happens. I think it is fine now actually
When you are ready to migrate your database to our SQL 2008 server don't forget about the SQL restore tool we have in the Winhost control panel. http://support.Winhost.com/KB/a771/how-do-i-generate-or-restore-a-backup-of-my-database.aspx
