Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Keepalive solutionsKeepalive solutions
Previous
 
Next
New Post
11/9/2007 6:57 AM
 
Petri Huila


www.webbplats.nu
Joined: 4/22/2004
Posts: 53

I have a DNN installation with several portals, both set up as child portals and parent portals with own domains. 
I have some issues with slow loading sites, and therefore I am trying some keepalive solutions as keepaliveforever.com
I have a question if you know how to configure it to keep the sites alive.

Do I need to set up all domains: 
www.domain1.com/keepalive.aspx
www.domain2.com/keepalive.aspx
www.domain3.com/keepalive.aspx
etc

Is this neccessary, or is it enough to "keepalive" one of the domains that are in the DNN installation?
 
Anyone who knows this?
 
New Post
11/9/2007 1:22 PM
 
Carlos Rodriguez

www.almacigo.com
Joined: 6/10/2003
Posts: 615

Petri:

Look at it from the point of view of an ASP.Net application, which DNN is of course.  If you are running all those sites from one physical DNN installation then keeping alive only one of the sites will keep all the DNN components in memory for that one installation.  If you have other sites on different physical DNN installation they you would have to keepalive only one site per physical install of DNN.

This is easy to test by the way, just define one domain for your keepalive solution, then in an hour or so try to access any of the other sites to see if they come up quickly or there is a delay.

Carlos

 
 
New Post
11/9/2007 7:30 PM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

I don't know how it is supposed to happen, but in my experience with a single DNN instance with a dozen or more portals,with all of their domains in the same app pool, I was also hoping that all sites would be responsive once any of them has started up.  But it isn't the case. Each domain still has its own startup time after being idle. I imagine that that is why the event viewer fills up with those purple startup and shutdown events all the time. They must be the individual sites.

I've found that starting up additional sites does not significantly increase memory usage... although CPU usage does ramp up during the process and settles down again after.

One other point noticed is if any domain is placed in a different app pool, the whole thing bogs down and CPU usage goes all the way up until the domains are organised properly again.

Maybe someone can shed light on exactly what's going on with all of this, as I also imagined that once the dll's were all loaded up for one domain in the instance.. that they'd then be loaded for all others.

Rob
 
New Post
11/14/2007 1:25 PM
 
Carlos Rodriguez

www.almacigo.com
Joined: 6/10/2003
Posts: 615

Robax:

I don't see why, when running multiple sites/domains with one installation of DNN, some sites would come up quickly and others do not. That is, if we are talking about just the application startup issue. Now, if one of those portals have a skin that is graphics intensive, that one is going to be slower than others with simpler skins. If you think about it, the application time out we are talking about is related to the loading of DLLs and allocation of related memory structures for the DNN application. If we are talking about multiple domains using the same DNN physical install, then they are using the same DLLs and same memory structures.

Another possible cause of delays unique to one site and not others is if there is one particular module that one site uses and the others do not. Also, different sites on the same install may have different caching settings for their modules.

Edit:  Forgot to mention that if the memory on the server is limited, it will swap memory pages out to disk regardless of the status of the keepalive timeout for the application.

Carlos
 
New Post
11/14/2007 1:41 PM
 
Will Strohl


Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

https://upendoventures.com
Joined: 3/1/2005
Posts: 2884

I too have a single DNN instance on a server with 3 sub-portals that each have their own domain.  Implementing a keep-alive solution on one of them DID NOT at all reduce the load time of the other 3.  Once they each had a keep-alive solution implemented, the inital load times were cut down drastically.  Also, it wouldn't hurt to use PageBlaster.

Here is a good blog and comments on keep-alives:

http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/135/HostTrackercom-No-Longer-Free.aspx

And this is just my two cents.  I do not care what is "supposed" to happen.  That is irrelevant when the evidence points elsewhere, and there are customers waiting.  Go with the solution that works and that addresses the TRUE problem - as long as it is not a work around.  ;)

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
 Page 1 of 4
1234Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Keepalive solutionsKeepalive solutions


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, 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 DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out