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
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Optimizng DNN for speed and performance Optimizng DNN for speed and performance
Previous
 
Next
New Post
9/5/2007 3:40 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

btw: did you read the skinning whitepaper, avaliable at Resources > Documentation page on this side. You will see, that skins are ASCX controls, that are only placed dynamically on the page. If you use caching and compression, I don't expect pages will load much slower than a static aspx.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/5/2007 5:28 AM
 
Baldwin Sun


www.sunblognuke.com
Joined: 2/21/2005
Posts: 197

leupold wrote

btw: did you read the skinning whitepaper, avaliable at Resources > Documentation page on this side. You will see, that skins are ASCX controls, that are only placed dynamically on the page. If you use caching and compression, I don't expect pages will load much slower than a static aspx.

I know the the skinning whitepaper and have read this document. I also consider the use of caching and compression.

But the result is not so good for our client. Any advice for Optimizng DNN for speed  and  performance?

I have no idea that if I bind the website to the some static skin which it load from the static  folder, this will make faster. More help and thanks for your reply!

sunblognuke v5 for dnn

Ultimate Blogging Module for DotNetNuke Platform
The professional provider of DotNetNuke support, skin design and custom module development.

 
New Post
9/5/2007 9:32 AM
 
Craig Walker


medfluent.net
Joined: 7/12/2004
Posts: 240

Unless you are dealing with a really complicated skin and/or have a lot of modules on each page, you may have another problem.  I have a site with over 200K users and thousands of pages.  We did add some additional indexes and are very strict about how new modules are developed, but I've never seen a skin be the cause of a performance issue (granted my skins are simple).  Before presuming the skinning engine is the problem, you may want to mke sure your dnn site is fully optimized.

I haven't used this personally, but this module on snowcovered, advertises to tune up your database.  There is also an Enterprise version with source.  For $15, this may be worth checking out.

I think everyone will agree, a dnn site will never be as fast as an all static site, but done properly, I don't think dnn skins cost much more than master page themes.

I have noticed, if you have a site with a lot of pages and you put a lot of modules on a single page and you have a lot of roles you will take a performance hit.  The page is just having to figure out a lot.  Again, though, this has nothing to do with the skin.
 
New Post
9/5/2007 9:18 PM
 
Baldwin Sun


www.sunblognuke.com
Joined: 2/21/2005
Posts: 197

Thanks for your reply and your advices!

But maybe I prefer a "portable" solution, meaning that the solution is not tied to any specific DNN version.  For example, if we upgrade to a new DNN version in the future (which can happen pretty often), we can apply our "performance enhancement" solution to the new DNN version without a lot of code change (though some moderate code change is OK).

I mean whether I can modify the architecture a bit to boost the skin performance or I give up the skin engine-drive. Is this possible and how difficulty it will be.

 O the contrary, I will try my best  to Optimizng DNN for speed  and  performance  based the skin mechanism exiting.

maybe currently we can consider these optimizations as follow:

(一)    One thing I have noticed is that the majority of the core modules use late binding expressions such
"<%# Databinder.Eval(Container.DataItem, "Name") %>"
to render data which uses reflection and is very slow.  It would be good to our module don't use reflection to bind data to datagrids, datalists, and repeaters.
(二)     One rule is to keep skin less then 10k. 5k if possible. I have done this several time for clients, and the sites still looks good.
Zero out portal.css(DNN portal default CSS) is great too.
(三)      Make you've only enabled necessary schedule items e.g. if you're not the search engine functionality, disable the SearchEngineScheduler etc.  These settings can be found in Host->Schedule
(四)    If  you're not using usersonline function, make sure it's unchecked in Host->Host Settings
(五)      If you're not using the sitelog (i.e.if you're using offline statistics such as webtrends), disable it by setting it to site log history to 0. If you do have to use it, consider setting its site log buffer to a value other than 1. This will cache the results, and only write periodically to the database. You risk losing some data i.e. if you have it set to 10, and at 8, you upload a new dll, the application will recycle, and you will lost those 8 records, but it does save a lot of database writes.
(六)       Use Caching, including module and tab page’s load.
( 七 ) make clean minimal skin. No heavy graphics, and ease the use of tables. If you use a skin made up with tables for layout, this will cause slower loading time .Go for a css design. That way the css will load only once when the page first loads, after that the css stay in the cache, on all other pages on your site the browser will not need to load the css from site, but from own cache. This will give you the fastest loading time
 ( 八 ) HttpCompression refers to a method of compressing data sent from your server then passing that data to the client browser where it is decompressed on the fly. Thus increasing the display speed of your pages by sending less data across the pipe.

 

 

sunblognuke v5 for dnn

Ultimate Blogging Module for DotNetNuke Platform
The professional provider of DotNetNuke support, skin design and custom module development.

 
 Page 2 of 2
Previous12 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Optimizng DNN for speed and performance Optimizng DNN for speed and 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.