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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN & Performance - ViewStateDNN & Performance - ViewState
Previous
 
Next
New Post
6/28/2006 10:58 PM
 
Synced:

What is your configuration? I mean, for the machine running DNN? If you are running it on your development PC, don't expect the greatest performance because of limitations of IIS and/or the TCP/IP stack related to serving HTTP requests. To get a fair idea of the performance you should run DNN on Windows server, and it doesn't even need to be very powerful.

Also, really basic but, are you running DNN in debug mode?

Carlos
 
New Post
6/29/2006 2:34 AM
 
I doubt Viewstate has lot to do with performance. Storing it in the session may improve it a little bit but if your site is really slow I would search elsewhere. What is slow and where is the site?
 
New Post
6/29/2006 10:42 PM
 

Hey gang. Thanks for the replies!

Well I am running the 4.x latest INSTALL zips, so are these in debug mode? I'm not running in VS.
I am just running on local host and finding it very very slow considering I have no traffic to the site and I am just browsing locally.

It takes a good 20 seconds sometimes for example if I click "Login" until I get the login form. After reading the article I posted to, the viewstate makes some sense. I would also like to remove it because if you think of any dialup users, if you are storing the session in a hidden form field, just looking at the viewstate on this very page doing viewsource and its HUGE.

I do not want this kind of overhead. From what I gather session viewstates (which most web technologies used in the past) uses more memory on the server. That is fine. I rather put the burden of memory on my server than make people post 50k up and down worth of viewstate. That and its just unwanted bandwidth. I think enabling/disabling the viewstate should be a choice of the admin of the site. They can choose between which advantages and drawbacks they require.

So that being said. How does one disable viewstate properly in 4.x branch without the bugs people are having trying to do so? Also I would like to benchmark it if its possible.

 
New Post
7/2/2006 1:22 AM
 

What OS are you running?  On my laptop starting up a 4.3.1 site takes 32 seconds - but I have a 2GHtz w/2 GB RAM and VS2005, SQL2005 Manager, Dreamweaver (with 6 open docs sucking RAM), outlook, 10 IE sessions, 5 FF tabs, and a number of background apps.  Once the site is up (after the process pool has recycled and the application has started) it takes less than 1 second on average to get the login page. 

My QA site over the net and through my PIX takes 12 seconds to start up and a second to get to the login page (a Win2k3 server dedicated to IIS). 

Make sure you're not just seeing the app restarts due to the fact no traffic on the site.  After a period (as defined in your app pool I believe - still trying to master this) the process is shutdown (recycled) to conserve resources.  If you're making changes to something and coming back periodically, it will take a bit to restart the application.  There are a number of posts on this - just search on keepalive or application start.  Go look at the admin logs for that event and see if that synchs with your issue timewise. 

Hope that helps. 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN & Performance - ViewStateDNN & Performance - 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