Coping with DNN application restarts

[RFH Reseller: Hollywood]

Hi All

We've got some downtime issues at present which we're working through with Warren.

However, beyond these issues we've also identified that the RFH setup is definitely shutting down DNN every 45 minutes as part of the scheduled application pool recycling.

Since even in it's new speedy 4.4.x form DNN takes
at least 30 seconds to restart, I'm wondering how much this will effect our site's performance, especially as we're ready to add some new forums to the site.

Does anyone have any practical advice on this? Is anyone running big DNN sites with forums, etc and can tell me what the user perception is of DNNs responsiveness under these situations? Does anyone have any tips for further reducing DNN start time?

Thanks for any advice that's out there

H :-)

[Staff: Warren Ashcroft]

We'll shortly be offering two new solutions for customers like yourself.

1) The ability for you to have your own secure and stable application pool on the web server - define your own recycle times controlling session timeouts etc..

2) The ability for you to have your own entire managed dedicated server located on our Helm controlled network, without any work - it acts and behaves like any other shared web server, except it isn't shared.

[RFH Reseller: Hollywood]

Thanks Warren. Given our current situation, that sounds like excellent news :-)

Would these features be offered as a standard option? Or would they cost more?

---

And I am also interested to know about any tips from others about how to optimise DNN sites to cope with the forced restarts. I know several people have commented how well their sites run here and I'm always keen to improve :-)

[Staff: Warren Ashcroft]

Both would be additional costing services, the first one would be quite cheap - only RAM in the server is additionaly consumed. The second would be around the same pricing as our dedicated server range.