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 ...Lookinf 4 advice on Compression, Caching and ViewstateLookinf 4 advice on Compression, Caching and Viewstate
Previous
 
Next
New Post
9/26/2006 9:18 AM
 

Hi,

I'm working with DNN 4.3.5 on Windows WK2003, ASP 2.0, IIS 6.0, SQL Server 2005 and Testing with Telerik Components.

I'm looking for help to complete my understanding of how to handle and combine three specific areas in DotNetNuke:

  1. Compression
  2. Caching
  3. Viewstate

1). Compression

Is it better to use IIS 6.0 for Http Compression?  Is there any drawbacks? Any peformance issues in a Hosted Environment?

I've looked at Blowery and presently looking at Snapsis Page Blaster (which combines compression with page cachnig).

2. Caching

If using module caching is there any need to enhance the BLL by adding data caching or Context to reduce the number of SP calls i.e.   Building a Categorzied List/Categorized Directory.

When Admin is logged in it will not cache data, other users cache data.   Does the "Authenticated Cacheability" on "Host Settings" setting come in here?

3). Viewtate

Having looked at blowery there seems to be only one easy way to handle Viewstate storage on the server by using Locopon's DSLocalizator. which stores viewstate in the database.

Any advice would be greatfully appreciated.

Cheers...


Colin Mulcahy
E: colin_mulcahy@hotmail.com
 
New Post
9/26/2006 9:32 AM
 
I use HTTPZip and CacheRight from www.port80software.com. In my view these tools are simply indispensable for an Admin.

No offence to the creators of the Blowery or Snapsis systems, but Port80's product maturity (and they have rabid customer support) make them the easy choice. They are a large company specifically geared towards IIS optimization.

Viewstate i'm not so sure about, however I was just reading the chapter from the WROX .NET 2.0 MVP Hacks book regarding viewstate hacks and they presented a couple options for optimizing it, I recommend that book (even if it's a little sparse in areas).


 
New Post
9/26/2006 10:22 AM
 
flyerstarter wrote
No offence to the creators of the Blowery or Snapsis systems, but Port80's product maturity (and they have rabid customer support) make them the easy choice. They are a large company specifically geared towards IIS optimization.


Comparing Port80 products and PageBlaster/Blowery is like comparing apples and oranges. They are meant for two totally different scenarios. Obviously, Port80's product is greatly superior, but requires you have control of IIS which is not applicable for shared hosting environments. PageBlaster/Blowery do not require any IIS setup or access, and thus are suited well for shared hosting situations. So its all about the specific use case.
 
New Post
9/26/2006 10:40 AM
 

I dont know your components but concerning the technologies you mention.
And now days I question any modules need 2,3,4 times before buying it.  Too many problems in the past.

These are my opinions only:

1)Compression-- if your looking to improve your performance there is probably somethign else you can do before doing this.  If you would like performance tips, ill be glad to help out. 

2)cacheing--  I assume you mean .Net caching.  Cacheing seems to remind me of the hassles we had with session in the asp 3.0 days.  Stay away from it if you can.  all may seem well, then one day the shiat hits the fan.  Use as a last resort

3)Viewstate -- Your best best, but depends on how you use it, meaning that view state can get messed up if the users are using your app in a way that might encourage it.  Such as having IE cache the settings.


DotNetNuke Search Engine
ASP.Net Search Engine
Email me to add your favorite sites to the search List.
 
New Post
9/26/2006 12:54 PM
 
Port80 also does not require any client setup if operated by the hosting company (in it's basic form).  For example you can turn on the HTTP compresssion as default for all new sites that are added in IIS.

You are right though, to take full advantage of it you need to be on the desktop or have a pretty friendly tech support.  It all depends what you're doing, and in a lot of my cases every drop of performance counts so having a few menus full of is required.


 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Lookinf 4 advice on Compression, Caching and ViewstateLookinf 4 advice on Compression, Caching and Viewstate


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