More than 40 seconds for each page ! Home Page too ! For the Forum page at least 55 secs !

I know we are dogfooding 5.1.0 beta (679 ?) but the end of tunnel seem to be really long.

Each days dnn loose interest and lose people interest in it.

Good luck, Sandro

---

Sandro De Matteis Microsoft IT Pro: Enterprise Admin, Enterprise Messaging Admin Technology Specialist: Microsoft Virtualization Dnn portals: http://www.dbdog.it , http://www.royalcrestgoldn.it, http://www.retrieversclub.it

I agree.  I see value in and fully support the use of dogfooding but continuing these exceedingly slow page response / loads for too long has a real potential to work against the core site interest of promoting DNN.  I hope the DNN team is considering the possiblity of un-dogfooding 5.1 if the problem goes on too long (more than a week?) without a resolution.
 
I'm not complaining for myself -- I'm more concerned with the potential for inappropriately (but understandably) casting DNN in a negative light.  A first-time DotNetNuke.com visitor considering DNN as a platform has no good indication that this slow performance is abnormal (or that a new DNN version is being "dogfooded" or even what "dogfooding" means) and is just as likely to believe all copies of DNN run this way all the time.....and then that visitor promptly heads off to Joomla land.  The visitor must think "Hey....if the guys that MADE it can't make it run any faster on their own site, what chance do I have?..."  Too much of a bad impression is bad for business which is why I care a lot more about others' perceptions of DNN over my own slow page load times during a dogfooding period. 
 
 
Also...
My DotNetNuke.com page load / response times are much better under Google Chrome than under either IE or FF.  Still painfully slow but somewhat manageable.  If you haven't yet tried Chrome, this dogfooding period seems like a good time to kick the tires...
 
-mamlin

---

esmamlin atxgeek.me

If it weren't a concern for new visitors, I would say keep it like this as long as the performance issue is actively being worked on and it's good for the long haul to iron out all the issues for 5.1.

For me, I just click a link and go do something else. Waiting for the page to load is not a good use of my time when a site is having a known performance issue. Plus it's a max of 5 posts I would read in one visit so no biggie.

It's not practical to stress test a secondary site if no one will visit it. Automated stress tests are very time consuming to set up if you need to test a ton of pages with hundreds of types of functionality.

I think it's a good idea to put a banner in every page header notifying users that the performance issue is known and it'e because the site is using a beta software. You don't want to turn away users coming in for the first time and leaving with a bad impression.