Register | Log In
Download Contact
Resources > Forums
HomeHomeGetting StartedGetting StartedNew to DotNetNu...New to DotNetNu...PerformancePerformance
Previous
 
Next
New Post
4/16/2012 7:29 PM
 
User is offline Matt Fette

Joined: 9/19/2007
Posts: 24
I have a site running DNN 06.01.04 (127) on GoDaddy with their delux hosting package.  The initial load time when I first access the site after a period of time (~ 1.5 hrs) can take from 10 to 30 seconds.  What are the top things in DNN I can do to improve performance on load and performance in general?
 
New Post
4/16/2012 8:50 PM
 
User is offline cathal connolly


cathal connolly's Avatar

cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 7400
please see http://www.dotnetnuke.com/Resources/Wiki/Page/Performance_best_practices.aspx - however I'm not sure how "delux" the godaddy account actually will be, there are a lot of people who have had better luck with other hosting providers, though many were on the basic godaddy package.
 
New Post
4/17/2012 7:39 AM
 
User is offline Mark Eckeard


Joined: 1/20/2004
Posts: 789
You can get a service to ping your website at certain intervals (15 minutes) and this will keep your website "alive".

Mark
 
New Post
4/18/2012 4:38 PM
 
User is offline Matt Fette

Joined: 9/19/2007
Posts: 24

I tried several of the suggestions for improving performance, but realized no improvement.  I asked GoDaddy to run an analysis on the site when first accessing it.  They said the site was doing a re-direct on initial load which was causing the delay.  Can someone provide me with the means to stop the redirect?

Thanks, Matt
 
New Post
4/19/2012 7:35 AM
 
User is offline Mark Eckeard


Joined: 1/20/2004
Posts: 789
It's not a DNN issue - it's .net. You need to keep traffic on your website in order to keep it alive, or in memory.

What I did was set up a small vb.net app that pings my website about 15 minutes before my staff comes in and this does the initial load of the website and there's no delay when they use it.

There may be some heavier caching on the DNN side that could help or you could even increase the timeout period in IIS to help.

Mark
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DotNetNu...New to DotNetNu...PerformancePerformance


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:

1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

Attend A Webinar
Start Professional Edition Trial
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke (DNN) provides a suite of solutions that make designing, building and managing feature-rich sites and communities fast, easy and cost-effective. The DotNetNuke Platform CMS is the foundation for more than one million websites worldwide. DNN Social, our newest solution, enables businesses to create immersive, interactive communities. Thousands of organizations like True Value Hardware, Bose, Cornell University, Glacier Water, Dannon, Delphi, USAA, NASCAR, Northern Health and the City of Denver have leveraged DNN to deploy highly engaging business- critical websites. Our rapid growth in product sales and deployments resulted in DotNetNuke Corp. being named one of the fastest growing private companies in America by Inc. Magazine in 2011 and 2012.
Copyright © 2002-2013 DotNetNuke Corp. / Terms of Use / Privacy
Hosted by MaximumASP