asp.net ajax 容器需要很长时间才能加载
我在单个屏幕中使用 2 个 asp.net ajax 选项卡容器来实现主要用于 Intranet 的 asp.net 应用程序。
事实是，最终它可能必须通过互联网访问，并且加载需要 15-17 秒，而通过互联网访问时，在 Response.Redirect() 之后需要 35-40 秒。在内网中一切正常。
我在双核服务器上的 IIS 6.0 和 Windows Server 2003 中使用 asp.net 4.0 以及来自 AjaxControlToolkit 版本 3.0.30930.0 的 tabcontainer。当从互联网使用应用程序时，我需要设置/执行什么操作才能使该网络控件正常工作？有什么特别的事情可能会破坏网络控制的性能吗？
I'm using 2 asp.net ajax tab container for a mostly intranet used asp.net application in a single screen.
Thing is, eventually it might have to be accesed through internet and it's taking 15-17 seconds to load and 35-40 seconds after a Response.Redirect() when it's accesed through internet. In intranet it works alright.
I'm using asp.net 4.0 with the tabcontainer from the AjaxControlToolkit version 3.0.30930.0 in IIS 6.0 and Windows Server 2003 on a Dual Core server. Is there anything I have to set/do for that webcontrol to work properly when the application is used from internet? Is there anything in particular which could screw that webcontrol performance?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
尝试使用 fiddler 之类的工具来查看服务器发送和发送的内容。听起来您的页面大小可能非常大，在快速的 Intranet 连接上工作正常，但在互联网上速度很慢。
如果出现以下情况，在服务器上启用压缩将会有所帮助是这样的。
Try using a tool like fiddler to look at what is being sent to and from the server. It sounds like your page size might be really big which works okay over a fast intranet connection but is slow over the internet.
Enabling compression on the server will help if this is the case.
如果内部工作正常，而外部（互联网）工作情况较差，那么您的问题很可能与您的 ISP 端或您的网络路径中的某个位置的网络相关......
If it is working fine internally and worse on the outside (internet), then it seems more likely that your issue is network related either on your ISP's side or somewhere in your path to the net...
什么可能会影响性能：
查找输出您从服务器/提琴手收到的内容。
不仅检查页面的大小，还检查激活/图像等的其他请求数量等。还要检查相关请求的大小。
如果不检查上述内容，很难说出继续的最佳方法。
我见过一些非常大的视图状态/其中一种情况甚至是由页面中使用的第三方控件引起的。
what could be screwing the performance:
Find out what you are receiving from the server / fiddler.
Check not only the size of the page, but also how many other requests are activated / for images, etc. Also check the size of the related requests.
Without checking the above is hard to tell the best way to proceed.
I've seen some awfully large viewstate / one of such cases was even caused by a third party control used in the page.
如果您放置许多包含大量内容的选项卡，每个选项卡可能会变慢，并且不会是 ajax tabcontainer 控制问题
if you place many tabs with large contents each one it'll likely turn slow and it wont be an ajax tabcontainer control problem