I'm willing to migrate my old custom-made cms (classic asp+sql server) to DNN.
The site is a city portal with more than 10k daily users and has 6000 registered users and 40k articles.
Now.. I really love DNN, it's what I was trying to do from scratch but only better, my only concern is performance.
It never happened to me that a local site, and even more a totally empty site, a fresh dnn install was so coumbersome and slow to load empty pages or do even the most basic tasks. This leaves me with the struggle to go on down the path of switching to DNN and eventually build my implementations as modules or carry on my .NET porting of my CMS (which of course is blazing fast even with 4 millions fake records in the db).
Since this is a real world scenario and a big step I will be taking, the site is already in production, I need some suggestions on my actual servers to understand if they will be able to handle the load.
At the moment I have 2 cloud istances for that. One is the db server with 8 cores 8 GB ram and several other DBs running but with low impact. The other istance is 4 cores 4 gb ram and is the web server with only 2 other sites with low impact as well.
Will this infrastructure be able to handle the load of 10k daily visits browsing 40k records? (I'm using EasyDNNNews at the moment to migrate the articles and I checked the procedures it does pagination sql server side so it whould be quite efficient).