20 Nov 2009
07 Jan 2011
Link to this post
We're getting some pretty bad page load times and trying to figure out why it's taking SF so long to return the initial page as well as many of the assets referenced by the page. There are tons of database queries happening on every page load, which is only going to be magnified when we have hundreds of users hitting the site at once. We're testing the old DNN site in parallel to the new SF site, and the SF site takes upwards of 10x as long to return the initial HTML (300ms as opposed to 30ms from DNN), and much much more than that on many of the CSS/JS/Image files...
1) Are there performance improvements in the works for the final release that will add more caching and reduce the number of database queries needed to serve a page? Even the static file requests are causing a bunch of database activity.
2) Why do the other assets (js/css/images) load so much slower when they are not burried in the App_Data folder? If you look at the attached image, the only files taking long to load are in ~/styles or ~/scripts... everything else loads fast. You'll also see two references to print.css... one in the theme folder, and one not. They take 1ms and 1.5sec to load, respectively. Any reason why SF would take so long to process a tiny CSS file?
I know it's just the RC, so I can be patient if there are improvements in the works, but please let us know if there's anything that can be done in the meantime. We are launching our site on RC2 on Monday...