巨大的HTML输出性能 [英] Huge HTML output perfomance

查看:66
本文介绍了巨大的HTML输出性能的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



我有一份报告,显示从数据库到浏览器的所有记录。

最终的HTML出来大约5兆。


当我用IE浏览页面时,转移显示需要1分5秒


跟踪信息显示输出在1秒内完成然后我猜测它需要花费很多时间(> 1分钟)来实际转移到IE。我正在同一台机器上进行测试。 IIS和IE在同一台机器上,我相信5 Meg数据的实际传输速度要快得多。


所以我怀疑所有的时间花在实际在ASP.NET引擎和IIS IO线程之间传输数据上。

有没有办法加快速度?


Bellow是跟踪信息,显示渲染时间不到一秒。

追踪信息来自最后的消息

aspx.page结束渲染0.802165 0.671952


谢谢

George。

解决方案

无论Web服务器是否与浏览器位于同一台计算机上,

HTTP都通过TCP连接。花费的时间是通过TCP连接发送5兆的数据作为HTTP响应所花费的时间。


基本上,问题是,你的网页太大了。


-

HTH,


Kevin Spencer

Microsoft MVP

..Net开发人员

你所寻求的是你所得到的。


" George" <无**** @ hotmail.com>在留言中写道

新闻:%2 **************** @ TK2MSFTNGP14.phx.gbl ...



我有一份报告,显示从数据库到浏览器的所有记录。

最终的HTML出来大约5兆。


当我点击页面时显示转移需要1分5秒

IE


跟踪信息显示输出在1秒内完成然后我猜

它需要花费很多时间(> 1分钟)来实际转移到IE。我在同一台机器上进行测试。
IIS和IE在同一台机器上,我相信实际转移的5 Meg数据要快得多。


所以我怀疑所有的时间都是用于在ASP.NET引擎和IIS IO线程之间实际传输数据



有没有办法加快速度?


Bellow是跟踪信息,显示渲染时间不到一秒。

跟踪信息来自最后的消息

aspx.page结束渲染0.802165 0.671952


谢谢

乔治。


blockquote>

更不用说传输数据了需要一段时间,浏览器还必须解析和处理5兆的HTML并正确呈现它。这与.aspx服务器端代码渲染不同 - 它只是创建生成的HTML。


鉴于此,你应该感到非常高兴它只需要一分钟这一切都发生了。我希望你们的客户都拥有非常快速的机器和良好的互联网连接。

" George" <无**** @ hotmail.com>在留言新闻中写道:%2 **************** @ TK2MSFTNGP14.phx.gbl ...



我有一个报告,显示从数据库到浏览器的所有记录。

最终HTML大约5梅。


需要1分5秒当我用IE浏览页面时转移显示


跟踪信息显示输出在1秒内完成然后我猜它花了这么多时间(> 1分钟)它实际上被转移到IE。我正在同一台机器上进行测试。 IIS和IE在同一台机器上,我相信5 Meg数据的实际传输速度要快得多。


所以我怀疑所有的时间花在实际在ASP.NET引擎和IIS IO线程之间传输数据上。

有没有办法加快速度?


Bellow是跟踪信息,显示渲染时间不到一秒。

追踪信息来自最后的消息

aspx.page结束渲染0.802165 0.671952


谢谢

George。


请允许我不同意。

我可以通过公司网络将该文件(生成的HTML)复制到1-2内的文件服务器秒。它确实穿越局域网(每秒100 Mbs)。


当IIS服务器与IE在同一台机器上时,数据通过TCP连接传输,但我可以向您保证实际速度比每秒100 Mb快得多。


所以我的观点是,5Meg的传输无法通过本地TCP连接花费超过一秒的时间。


乔治。


" Kevin Spencer" <柯*** @ DIESPAMMERSDIEtakempis.com>在消息新闻中写道:ui ************** @ TK2MSFTNGP15.phx.gbl ...

无论网络服务器是否与浏览器,

HTTP通过TCP连接传输。花费的时间是通过TCP连接发送5兆的数据作为HTTP响应所花费的时间。


基本上,问题是,你的网页太大了。


-

HTH,


Kevin Spencer

Microsoft MVP

.Net开发人员

你所寻求的是你所得到的。


" George" <无**** @ hotmail.com>在留言中写道

新闻:%2 **************** @ TK2MSFTNGP14.phx.gbl ...



我有一份报告,显示从数据库到浏览器的所有记录。

最终的HTML出来大约5兆。


当我点击页面时显示转移需要1分5秒

IE


跟踪信息显示输出在1秒内完成然后我猜

它需要花费很多时间(> 1分钟)来实际转移到IE。我在同一台机器上进行测试。
IIS和IE在同一台机器上,我相信实际转移的5 Meg数据要快得多。


所以我怀疑所有的时间都是用于在ASP.NET引擎和IIS IO线程之间实际传输数据



有没有办法加快速度?


Bellow是跟踪信息,显示渲染时间不到一秒。

跟踪信息来自最后的消息

aspx.page结束渲染0.802165 0.671952


谢谢

乔治。



Hi,
I have a report which shows all records from database into the browser.
The final HTML comes out about 5 Meg.

It takes 1 minute 5 seconds for transfer to show up when i hit the page with IE

The trace info shows that output was done within 1 second and then i guess it took so much time (> 1 minute) for it to actually be transferred to IE. I am doing test on the same machine. IIS and IE are on the same machine and I believe the actual transfer of 5 Meg data is much faster.

So i suspect that all that time was spent on actually transferring data between ASP.NET engine and IIS IO threads.
Is there a way to speed up that?

Bellow is info from trace that shows the rendering took less than a second.
Trace info Message From First From Last
aspx.page End Render 0.802165 0.671952

Thanks
George.

解决方案

Regardless of whether the web server is on the same machine as the browser,
HTTP is transported over a TCP connection. The time spent was the time it
took to send 5 megs of data over a TCP connection as an HTTP response.

Basically, the problem is, your web page is too big.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.

"George" <no****@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
Hi,
I have a report which shows all records from database into the browser.
The final HTML comes out about 5 Meg.

It takes 1 minute 5 seconds for transfer to show up when i hit the page with
IE

The trace info shows that output was done within 1 second and then i guess
it took so much time (> 1 minute) for it to actually be transferred to IE. I
am doing test on the same machine. IIS and IE are on the same machine and I
believe the actual transfer of 5 Meg data is much faster.

So i suspect that all that time was spent on actually transferring data
between ASP.NET engine and IIS IO threads.
Is there a way to speed up that?

Bellow is info from trace that shows the rendering took less than a second.
Trace info Message From First From Last
aspx.page End Render 0.802165 0.671952

Thanks
George.



Not to mention that transferring the data takes quite a while, the browser also has to parse and process 5 megs worth of HTML and render it properly. That is not the same thing as the .aspx server side code rendering - that just creates the resulting HTML.

Given that, you should be very happy that it is taking only a minute for all this happen. I hope your clients all have very fast machines with excellent internet connections.
"George" <no****@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP14.phx.gbl...
Hi,
I have a report which shows all records from database into the browser.
The final HTML comes out about 5 Meg.

It takes 1 minute 5 seconds for transfer to show up when i hit the page with IE

The trace info shows that output was done within 1 second and then i guess it took so much time (> 1 minute) for it to actually be transferred to IE. I am doing test on the same machine. IIS and IE are on the same machine and I believe the actual transfer of 5 Meg data is much faster.

So i suspect that all that time was spent on actually transferring data between ASP.NET engine and IIS IO threads.
Is there a way to speed up that?

Bellow is info from trace that shows the rendering took less than a second.
Trace info Message From First From Last
aspx.page End Render 0.802165 0.671952

Thanks
George.


Allow me to disagree.
I can copy that file (generated HTML) over our corporate network to a file server within 1-2 seconds. And it really does travels across the LAN (100 Mbs per sec).

When IIS server on the same machine as IE the data transfers over TCP connection but i can assure you that actual speed is much faster than 100 Mb per sec.

So my point is that there is no way that transfer of 5Meg took more than a second over a local TCP connection.

George.

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message news:ui**************@TK2MSFTNGP15.phx.gbl...
Regardless of whether the web server is on the same machine as the browser,
HTTP is transported over a TCP connection. The time spent was the time it
took to send 5 megs of data over a TCP connection as an HTTP response.

Basically, the problem is, your web page is too big.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
What You Seek Is What You Get.

"George" <no****@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
Hi,
I have a report which shows all records from database into the browser.
The final HTML comes out about 5 Meg.

It takes 1 minute 5 seconds for transfer to show up when i hit the page with
IE

The trace info shows that output was done within 1 second and then i guess
it took so much time (> 1 minute) for it to actually be transferred to IE. I
am doing test on the same machine. IIS and IE are on the same machine and I
believe the actual transfer of 5 Meg data is much faster.

So i suspect that all that time was spent on actually transferring data
between ASP.NET engine and IIS IO threads.
Is there a way to speed up that?

Bellow is info from trace that shows the rendering took less than a second.
Trace info Message From First From Last
aspx.page End Render 0.802165 0.671952

Thanks
George.



这篇关于巨大的HTML输出性能的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆