|
|
Posted by Dan Guzman on 09/04/05 19:21
> This means that all of
> the slowness must be in the transmission of the data from the CF server
> to the client web browser plus the time it takes for the browser to
> render the page.
If your resultset is large, it can take considerable time to render the data
in the client browser. One easy method to see if this is the reason for the
slowness is to save the page to disk and then open the file.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"robboll" <robboll@hotmail.com> wrote in message
news:1125802032.776460.7050@g49g2000cwa.googlegroups.com...
> Some additional information:
>
> I turned on debugging info for Cold Fusion and the query itslef is
> processed in about 300 ms, so the sql server is not the problem.
> According to the CF server, it is taking about 950 ms total to execute
> the page (including the query). The total is still less than a second,
> so even the CF server shouldn't be the problem. This means that all of
> the slowness must be in the transmission of the data from the CF server
> to the client web browser plus the time it takes for the browser to
> render the page. IIS may even be part of the problem because it
> handles the incoming requests before it hands over execution to the CF
> server.
>
> Has anyone dealt with this issue before? Any suggestions to improve
> the speed/performance?
>
> RBollinger
>
> robboll wrote:
>> Whenever I query my database using Enterprise Manager, the response
>> time is about a second. When I access the same data via a Cold Fusion
>> webpage, it takes about 15 seconds (or more) to resolve. I created an
>> index for the fields involved in the query and updated statistics. It
>> makes no difference. Is there anything else I should look at? The
>> table is only about 3000 records. Any suggestions to speed up queries
>> when using Cold Fusion? Thanks for any help with this.
>>
>> RBollinger
>
Navigation:
[Reply to this message]
|