aspnet_wp.exe Issue

[Jennifier]

I build an asp.net web application which most pages are reports. I use xml server control and xsl to show the reports. I got a problem: If the report consists of several thousands records, aspnet_wp.exe perocess will keep using CUP up to 99%, and blocks all other processes. I do not know how to solve the problem, anybody has a good idea? Also I would like to know if I use web form (eg, Datagrid to show the reports), the performance is better or worse than xsl? Thanks in advance!

[Kevin Spencer]

There is just no good reason to spit several thousand records onto a single
web page. You need to limit the number of records you are sending at one
time to the client in your app.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.

"Jennifier" <an*******@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...

I build an asp.net web application which most pages are reports. I use xml

server control and xsl to show the reports. I got a problem: If the report
consists of several thousands records, aspnet_wp.exe perocess will keep
using CUP up to 99%, and blocks all other processes. I do not know how to
solve the problem, anybody has a good idea? Also I would like to know if I
use web form (eg, Datagrid to show the reports), the performance is better
or worse than xsl? Thanks in advance!

[Alvin Bruney]

Kevin is right, you are getting killed in the on render portion as cpu tries
to keep up with all that data. You may want to use a paged data grid. This
will help because only page one is rendered and cpu doesn't peg. A user
cannot possibly comprehend 1000 rows of information by the way.

--
-----------
Got TidBits?
Get it here: www.networkip.net/tidbits
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:OW**************@TK2MSFTNGP10.phx.gbl...

There is just no good reason to spit several thousand records onto a single web page. You need to limit the number of records you are sending at one
time to the client in your app.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.

"Jennifier" <an*******@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...

I build an asp.net web application which most pages are reports. I use

xml server control and xsl to show the reports. I got a problem: If the report
consists of several thousands records, aspnet_wp.exe perocess will keep
using CUP up to 99%, and blocks all other processes. I do not know how to
solve the problem, anybody has a good idea? Also I would like to know if I
use web form (eg, Datagrid to show the reports), the performance is better
or worse than xsl? Thanks in advance!