G
Greg
I am researching the response time of a pivot page using
different data load methods (client oracle oledb, csv file created
serverside by asp,..)
My pivot loads its structure from the XML data, then goes to the db or file
for its data.
After choosing a report the empty pivot object pauses for a period and then
the small colored cube begins to spin in the upper-left corner of the
object. finally the cube stops, and in a short instance the pivot is
rendered.
Can anyone confirm what is happening during each stage?
Here is my guess:
1. The period before the cube spins represents the time to get the XML data
and load it into the pivot object on the client.
2. The spinning cube represents the time to get the data from the data
source (oracle oledb, or csv/asp, ....)
3. The period between the spinning cube stopping and the display of the
pivot/chart is rendering time on the client.
My response time appears tremendously slower (10 times) in getting data from
static csv file on webserver when compared with the OLEDB connection that
leverages the Oracle client.
I expected about the same. It will only get slower when I convert the to
using an asp page to generate the csv file on the fly. Has anybody figured
out a fast way to load big data sets?
different data load methods (client oracle oledb, csv file created
serverside by asp,..)
My pivot loads its structure from the XML data, then goes to the db or file
for its data.
After choosing a report the empty pivot object pauses for a period and then
the small colored cube begins to spin in the upper-left corner of the
object. finally the cube stops, and in a short instance the pivot is
rendered.
Can anyone confirm what is happening during each stage?
Here is my guess:
1. The period before the cube spins represents the time to get the XML data
and load it into the pivot object on the client.
2. The spinning cube represents the time to get the data from the data
source (oracle oledb, or csv/asp, ....)
3. The period between the spinning cube stopping and the display of the
pivot/chart is rendering time on the client.
My response time appears tremendously slower (10 times) in getting data from
static csv file on webserver when compared with the OLEDB connection that
leverages the Oracle client.
I expected about the same. It will only get slower when I convert the to
using an asp page to generate the csv file on the fly. Has anybody figured
out a fast way to load big data sets?