Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Once and for all - letOnce and for all - let's find a keepalive solution that will actually keep alive.
Previous
 
Next
New Post
4/1/2007 9:38 PM
 

Yes it is a bit of a drag.
The blame should not be put entirely on ASP.Net though. 
DotNetNuke is a large application that really takes a lot longer than most ASP.Net applications to do the compile and initial load after it has been cycled down.

Still, it's not impossible to have a fast loading site. Check out mine:  http://www.snapsis.com

According to Alexa it loads faster than 78% of the sites on the internet http://www.alexa.com/data/details/main?q=&url=snapsis.com/  -- 1.1 seconds average, but on a fast connection it is always in the sub-second range.

 


DotNetNuke Modules from Snapsis.com
 
New Post
4/1/2007 11:33 PM
 

JennaM:

I think you are making a really big deal of an issue that is very easy to resolve, and I can understand the frustration.  It is for that reason that when I decided to take care of the problem once and for all for the sites I host on my server, I wrote a little console program in VB.Net.  I then created a scheduled task to run that program every 15 minutes.  The program uses an old fashion INI file where I can enter the URLs I want to invoke.  In the case of DNN, I enter the URL as www.domain.com/keepalive.aspx.  Calling the Keepalive.aspx is very efficient for this purpose since it will keep the site in memory but only returns the date and time when invoked.  And you could run it from any PC or server that is up all the time since the call to the Web site is a standard HTTP call.

If you wish to use my program I can send it to you.  I have not put it on my site for download because it needs some cleaning up but it just works.  Let me know, if you haven't abandoned ASP.Net altogether that is...

Carlos

 

 
New Post
4/2/2007 12:43 AM
 
I'm probably not going to be adding a whole lot to this thread, but I'll give my solution, which seems to have been touched on, but in general brushed off.
I use SmarterPing to keep my site alive on a shared host.
There may be some ignorance on my part as to why it seems that everyone has been suggesting that SmarterPing is only an elegant solution for a dedicated server, but it works fantastic for me.
"Ahhh", says I. I get it. Where do you run SmarterPing?
I have a desktop at home that is always on and connected (firewalls, ect). So I just run SP on that. Yay for answering my own question.
My other method I use, in conjunction with SP; since SP has no reporting; is Siteping,com.
A free account lets you 'ping' 3 different sites, to keep them alive and check their status. It does do reporting and whatnot, which wasn't really wanted.

Just my thoughts.
 
New Post
4/2/2007 1:26 AM
 
try ://www.keepaliveforever.com/, I think they might be what you are looking for.
 
New Post
4/2/2007 11:04 AM
 

I use host-tracker.com they do a great job, and it is free.  I also get uptime precentages as well as email notifications when the site is down.

It keeps the site alive as well!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

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

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Once and for all - letOnce and for all - let's find a keepalive solution that will actually keep alive.


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