Armin Rahimian wrote:
Sebastian Leupold wrote:
The first line is the time, until the server has evaluated the call and composed the page, starting to transfer content
Exactly. This is my big question. Why server has evaluated the call and composed the page for 9-12 Seconds and just about 2 second page opening!
All kind of DNN Portals have a same result and this line in other websites is 1-3 seconds....!
Actually I don't know DNN how do processing files and how to connect to database, but I think there is a problem in structure or calculating and it is cause to take time. I saw other website with 180 Requests and 1MB was 3.82 Seconds and my DNN with very good configuration and 78 requests and 1.6MB was 14 Seconds!!!! It's really show us a problem isn't it?
Maybe DNN has single task processors or not use full CPU resource and several other things that to make delay on calculating. Please explain about this problem, I think really need to Redesign DNN structure.
If DNN has huge Resource to make very user friendly CMS, I'm sure there is a way to customize or detect useful part of resource to sending for render and process and make short time.
:( There friends, I looking for a way to solve dnn speed problem. we need to fix it and we need NEW WAY...
Armin,
please be aware, that a lot of processing has to be done until a page get displayed to the public: DNN needs to evaluate URL and look up page details and list of modules in the database. It needs to check permissions and get content for each module (again, from the database). it needs to render content of each module, combine it inside the skin and send the rendered page to the client. The key to improve this behavior is caching. DNN tries to cache results from the database, but you may improve performance of your pages by setting up output caching for modules and pages properly. Whenever a module supports caching, you should enable it in Module Settings. If you are having pages, which are completely user-independent, you should consider page output caching (using a 3rd party page caching provider).
To get around initial load time after a the application has been recycled, disable recycling the app after 20 minutes of no activity (enable a fixed time recycle in the night instead), setup a site tracking service, that hits the home page every 15 minutes to make sure, it gets loaded after nightly or other page recycle.