Your question has been submitted and is awaiting moderation.
Hi DNN Community -
I have DNN 5.6.3 running on my local computer (localhost). I made a duplicate copy in a new folder, then updated it to DNN 7.1 (localhost:82). Update went smoothly. I am running both instances on the same machine (both under .NET Framework v4.0.30319 | "Integrated" pipeline mode).
I then clicked on 10 pages of the DNN 5.6.3 site, with the Task Manager open, and it went up to 162.5MB of memory.
I then opened the DNN 7.1 site and visited the same 10 pages, and it was up to 368MB of memory.
After clicking around vigorously on the 5.6.3 version, it never went above 200MB of memory, while clicking around vigorously on the 7.1 version, it went over 500MB.
My Local computer has Windows 8 operating system, and IIS 8.0.
I have gone though the DNN7.1 instance and tried to make performance tweaks as described on Matt Jura's site (http://www.mattjura.com/how-to-optimise-dotnetnuke-7-site-for-speed-by-improving-page-load-caching-and-use-of-cdn). The speed improved after these updates, but the site is still using quite a bit of memory compared to the DNN 5.6.3 version.
Does anyone have some ideas about what might have caused the higher jump in memory after upgrading to DNN 7.1? I don't want to move the update into production, since I have multiple instances running in production, and I am worried that upgrading will cause "out of memory" issues on the dedicated server. I can set the app pools to recycle after it hits 200MB of memory, but then the app pool will be recycling every time someone visits more than 3 pages.
I am open to any ideas, suggestions, ect.