DNN Initial load speed... very slow - Chat About It!

Forum General DotNetN... Chat About It! DNN Initial load speed... very slow

7/8/2008 9:18 AM

	Mitch Sellers
5818 posts
www.mitchelsellers.com

Re: DNN Initial load speed... very slow

As mentioned above, the startup time shouldn't be a big issue, as long as the application doesn't timeout on a regular basis.

The above recommendations will work.

Another option would be to use a keep-alive service such as Pingdom.com or host-tracker.com

-Mitchel Sellers
MCITP, MCPD, MCTS
CEO/Director of Development - IowaComputerGurus Inc.

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Consulting Quotes, and DNN Technical Support Services

I reccomend 3Essentials for shared hosting and BaseCamp for project management

7/8/2008 10:17 AM

	riprod
50 posts

Re: DNN Initial load speed... very slow

OK, I think I found my problem. Or at least one of them.

1. I have set the application pool as described but it still seams slow. Very slow (20 - 25 sec) on the 1st load. 8 to 10 sec on each additional. So I have another problem.

2. I checked my even log and found the following errors. It seams the Media module is causing problems even though I am not using it. Any ideas :

EventQueue.ProcessMessage: Message Processing Failed
ProcessorType: DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass: DotNetNuke.Modules.Media.MediaController, DotNetNuke.Modules.Media
DesktopModuleId: 63
UpgradeVersionsList: 03.02.00,03.02.03
ExceptionMessage: Value cannot be null. Parameter name: type
Server Name: PE1950

______

AssemblyVersion: 04.08.04
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /InternalForum/tabid/100/forumid/1/threadid/2/scope/posts/Default.aspx
AbsoluteURL: /InternalForum/tabid/100/forumid/1/threadid/2/scope/posts/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: de946daa-bb70-40ad-906f-7a41b0851af9
InnerException: Could not load file or assembly 'DotNetNuke.Modules.Media' or one of its dependencies. The system cannot find the file specified.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.RuntimeTypeHandle._GetTypeByName
StackTrace:
Message: System.IO.FileNotFoundException: Could not load file or assembly 'DotNetNuke.Modules.Media' or one of its dependencies. The system cannot find the file specified. File name: 'DotNetNuke.Modules.Media' at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) at System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Source:
Server Name: PE1950

_____

7/8/2008 11:18 AM

	lanceomagnifico
29 posts

Re: DNN Initial load speed... very slow

If you can, unistall the media module if you're not using it. Quickly looking at the event, it looks like the Media module may not be installed correctly.

There are a few tools you can use to diagnose a slow ASP.NET website. The first I would look at is using the inbuilt 'trace' functionality. It will tell you *exactly* how long different sections of the code takes to run. Using this knowledge, you can then dig into the code to find the culprit.

To enable it, you'll have to put the following into your root DNN web.config :

<configuration>
    <system.web>

...
        <trace enabled="true" localOnly="false"/>

...
    </system.web>
</configuration>

Once you've done that, browse a couple of pages on your site and then navigate to www.blahblah.com/trace.axd to view the trace info.

NOTE: Before you do this, you should read up on ASP.NET tracing, the performance and security implications.

Page 2 of 2

Forum

General DotNetN...

Chat About It!

DNN Initial load speed... very slow