I have been running the company CRM application using our custom Controls/Engine/Providers since DNN 1.x.

Our production site is currently running version 3.2.2 and there are about 450 concurrent users all day long. DNN usually responds in about 1 second per page request that is really good considering the communication with our legacy app.

Recently we moved our main Call center (150 users) to a new instance running the release candidate 3.3.2, and the results were extremely bad. The performance was pretty good with a small amount of users but when we reach the final amount of users, the site was unresponsive, and was taking about 10 seconds to respond to a simple "login" request.

We use our on dedicated hardware for the DNN instance, and it was noticeable the bigger amount of resources being used on our CPUs.

I also detected a similar behavior I have been noticed since "www.dotnetnuke.com" migrated to DNN 4.3.2.... In some occasions the web pages doesn't respond at all, and the web browser stays there waiting forever... I always have to resend the request from the browser in order to get a response from the site.

There were no errors detected on the logs (Neither the event viewer or the DNN log viewer) and at peek times some modules start disappearing from our tabs.

I only want to notify to the core member team to review the issues before the final release.