Slow response times

Hello,

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...

Thanks,
Matt

Hello Matt,

With the official release you'll be able to use the output cache for pages which will solve some of the issues.
We will try fix to fix  the other perfomance issues in Q1. We started investigating the issue and I believe that some of the fixes will be included in out weekly builds.

Best wishes,
Pavel
the Telerik team

We've been playing with the output cache combined with a substitution control for the user specific links, and this is definitely going to help a bit on the response times under heavy load.  But we're still experiencing way too much database activity, and considering adding another CPU to the database server to support this system.

I have a static HTML file that references nothing but static content.  Firebug shows about 30 references to images, scripts, and style sheets that are downloaded from our own custom folders within the site.  SQL Server profiler shows about 150 database hits while serving this page.  Once again this is a static HTML page with only static content, no database queries or server tags or any Sitefinity content or controls.  This is just one example... some of our dynamic pages are producing several hundred queries.  Needless to say, our load testing results have been horrendous, and we're contemplating spending more money on hardware if this doesn't improve soon.  Output cache is just a band-aid that only partially covers up the problem... doesn't even help with the static content, and doesn't help with the first load or subsequent refreshes.  You should have caching in every layer of the system... don't leave all the performance tuning up to us.  Please tell me this is all going to get better soon?

Thanks,
Matt

Hi Matt,

We are actively working on finding the bigger memory consumption and the resources usage as a whole. It will be very helpful if you can provide us with a feedback, because your case is quite real, and such cases matter most. 

Can you please elaborate on the static HTML file? How is it included in navigation, and what scripts does it use? Is it a physical html file, on the file system?

Greetings,
Georgi
the Telerik team