ASP .NET 2.0 Performance

  • Thread starter Thread starter Roman
  • Start date Start date
R

Roman

I am looking to improve the performance of my application. The result
page is 17k but it takes years to come up. There is an underlying sql
2005 query, but results come back rather fast. It seems to me that
caching is not there. Any suggestions?

Thanks in advance
 
Hi Roman,

Are you saying 17000 records. First thing do not know what a user will
do by viewing 17000 record at one glance. Best will be to pagination. I
mean 10 record at one time

As you said SQL 2005 there is a concept called as SQL cache dependency
but wondering do you really require that.

Regards
Shiv
Free 1000 .NET and SQL Server Interview questions with answers
http://www.questpond.com
 
Thanks for your help. I meant 17kb as rendered file size to say it
didn't generate much traffic.

As for the database, it is tiny. Also, other pages which do not query
the db perform the same way. It appears that application server is
building the page every time even if it didn't change.

Thanks again
 
Roman said:
Thanks for your help. I meant 17kb as rendered file size to say it
didn't generate much traffic.

As for the database, it is tiny. Also, other pages which do not query
the db perform the same way. It appears that application server is
building the page every time even if it didn't change.

Thanks again
Click to expand...

Hi Roman,

Just to clarify, are you running this app from iis, or through the
development webserver in vs2005? If you are running it from iis, does
the page take a long time to load each time you view it, or on first
view?
 
ack,

ignore my question! I normally post on the asp forums and thought I was
reading this there.

Sorry about this :)
 
It takes long to load each time I view it.

^MisterJingo^ said:
Hi Roman,

Just to clarify, are you running this app from iis, or through the
development webserver in vs2005? If you are running it from iis, does
the page take a long time to load each time you view it, or on first
view?
Click to expand...
 
Hi,

Without seeing the code we can solve nothing, of course nobody will have the
time to see the entire code so this mean you will have to do some profiling
yourself.

A very simple way of doing this is by wrapping key parts of your app with
DateTime instances and checking the Ticks :
DateTime start = DateTime.Now;
// your code
TimeSpan span = DateTiem.Now.Substract( start);
 
Roman,
Turn on page tracing and do some Trace.Warn 's at strategic locations in the
code showing where the page is at and the times.
Peter
 
Thanks for your help. Is there a way to tell what pages/page parts
were cached in IIS? How does IIS decide, without rendering the page,
that this page has changed and it needs to be reloaded?
 
In the previous reply I meant to say this is great.

I have one more question.

Assuming you had established caching duration as 1 hour. What happens
if during this time the cached page changed and conversely if caching
duration expired and page didn't change?

Thanks in advance
 
Back
Top