I'm hoping to get some advice on how to deal with ASP.NET's compile lag time in regards to clients, or potentially losing clients or getting fired for using .NET & DNN. If anyone wants to take a shot at my 5 points below -- I believe this covers all the issues.
A client sent me an email today:
Jason, that
took forever to load. The first time I went to www.xxx.com it did not load at all, then
went to xxx.com and it finally loaded.1. One thing I'm concerned about is "did not load at all?" I have seen this with DNN, but I figure a timeout is acceptable the first time going to it. Once a website gets visitors it's not a problem.
2. But, what about that 1000th customer that happens to hit the website when a change is made or when the app pool recycles every 2700 minutes? I don't think even keep alive programs can prevent this?
3. Also, this is disconcerting (embarrassing) when clients I set-up a new DNN site for is ALWAYS getting this 30-60 second lag (since there is no traffic). This is hard to explain away!
4. Another issue though is Intranet websites where maybe you only have 30 employees. I can see this Intranet not getting used that often and seeing waiting for the .NET app to compile.
5. I did a search on Microsoft's knowledge base, but didn't find anything under "slow" and ".NET." It would be great to get a resource I could link the client to. I'm betting my career in the hands of DNN and .NET.