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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...improving DNN startup performanceimproving DNN startup performance
Previous
 
Next
New Post
4/3/2007 10:35 PM
 
I think start up performance would be much improved if the DNN core pages could be pre-compiled. Are there any plans to support this as this in a future release? It could help significantly reduce some of the initial load times ASP.NET requires to compile the pages after the worker process is recycled.
 
New Post
4/7/2007 7:29 AM
 
If you are interested in PageMonkey you can get at http://www.sdcsol.com/Default.aspx?tabid=186
 
New Post
4/7/2007 8:43 AM
 

Page Monkey Sounds like a nice utility. I thought of building this also, but can never seem to find the time.

I would be interested in testing it out.

Can you also comment on yout option number 5, what does it cache - I have had problem with the user role caching and dynamically creating users in the past.

Thanks - can't wait to spin up DNN 4.5!!


Jim www.walkspoiled.com
 
New Post
4/7/2007 9:16 AM
 
jbonnie,

My understanding is:::

Private means page content is cached at each client - not on the server. Ideally you could use public - cached both on the server (so the cache could be shared) and on the client. If the server caches then clients can leverage this shared caching and performance is actually further improved. Depends on the resources available to your server. In a hosted environment it is usually limited so I dont like to make the server do anything more than it has to.

The default DNN setting is "server and no cache" for some reason which would mean the server does all the caching and the client does nothing.

I'm in favor of having the client share in the work load so I like the private or public settings. My experience is that both work much better than the "server and no cache" in my environment.

No cache would mean nobody caches anything which basically sucks.

Of course... your mileage may vary depending on your setup.

Also see http://support.microsoft.com/kb/247404
 
New Post
4/8/2007 9:42 AM
 

Drollins,

Thanks for the detailed explanation and the link to the Microsoft article.

I will definitely need to schedule some testing with the different host and iis settings for my application.

We are getting ready to launch on an intranet in the next 2 months.

 


Jim www.walkspoiled.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...improving DNN startup performanceimproving DNN startup performance


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