W
William A. Sempf
Hi, everyone. Posting this in the IIS group, because I don't think it is an
ASP.NET question, crossposting because I am not sure. Apologizing in
advance.
I have a page with a datagrid that binds to a dataset that is generated from
an Oracle database. If I trace the page load, and run ACT, the trace shows
that the dataset load takes 9 seconds, and ACT says the page returns in 10.6
seconds.
So I cached the dataset. On the first page load it is the same as above, as
expected. Now on the second page load the dataset load takes zero seconds
(Whole page render takes 1.1 seconds) and ACT says the page returns in ...
seven seconds.
What's up with that? Logically, since I dropped off the 9 second dataset
load, I had a net GAIN of 5.4 seconds by caching. According to trace, the
page render, from beginning to end, takes 1.1 seconds. Where are those
other seconds going to?
ASP.NET question, crossposting because I am not sure. Apologizing in
advance.
I have a page with a datagrid that binds to a dataset that is generated from
an Oracle database. If I trace the page load, and run ACT, the trace shows
that the dataset load takes 9 seconds, and ACT says the page returns in 10.6
seconds.
So I cached the dataset. On the first page load it is the same as above, as
expected. Now on the second page load the dataset load takes zero seconds
(Whole page render takes 1.1 seconds) and ACT says the page returns in ...
seven seconds.
What's up with that? Logically, since I dropped off the 9 second dataset
load, I had a net GAIN of 5.4 seconds by caching. According to trace, the
page render, from beginning to end, takes 1.1 seconds. Where are those
other seconds going to?