Most ASP developers already know that maintaining state in ASP pages comes
at a performance cost and that you should avoid persisting state when it
makes logical sense to do so. But did you know that you could be paying a
performance cost for state management even when your code isn't using it?
The issue is that the ASP engine makes room for the possibility you'll use
state management features of the session object even if you never refer to
any of them in code. So, if you know that you aren't using state at all,
you should add the directive
<%@ EnableSessionState = False %>
to any page that doesn't require the session object. This declaration allows
ASP to process scripts concurrently instead of sequentially and will improve
overall performance.
State vs performance in ASP
By ElementK Journals, published on 14 Jul 2001
| Filed in
You might also like...
ASP (3.0) forum discussion
-
Invitation to take part in an academic research study
by researchlab (0 replies)
-
How to insert & edit unique value using store procedure
by umeshdaiya (0 replies)
-
How to troubleshoot Epson laser printer?
by daisywyatt618 (0 replies)
-
view state is stored after the page post-back
by shriniwas.khatri852 (0 replies)
-
Transfer selected rows from one GridView to another GridView in aspxform(ASP.NET)
by dorsa (0 replies)
ASP (3.0) podcasts
-
Hanselminutes: Startup Series: Buying an Existing Small Company or Online Application
Published 8 years ago, running time 0h34m
Scott talks to Rob Walling about how he purchases small niche products and companies online and revitalizes them. He recently purchased an existing product that consisted of a 300 gig database and tens of thousands of lines of Classic ASP. How did he know it was valuable? What's next?
Comments