Google Chrome 无法加载网页，因为 myPortalapps-12812b1f934c6c.myPortal.apps.com 响应时间过长
Google Chrome could not load the webpage because myPortalapps-12812b1f934c6c.myPortal.apps.com took too long to respond
尝试使用 hello world 托管应用程序，但在部署时遇到此错误，
Google Chrome could not load the webpage because
myPortalapps-12812b1f934c6c.myPortal.apps.com took too long to respond
我可以 ping myPortalapps.myPortal.apps.com 但不能 ping myPortalapps-12812b1f934c6c.myPortal.apps.com
Sharepoint 网络应用程序 this forum post 帮助我解决了很多问题：
我也遇到了一些类似的问题
When troubleshooting performance issues where more than one
person/computer is impacted, the first place I like to start is by
running a sniffer like Fiddler:
http://www.fiddler2.com/fiddler2/version.asp
Fiddler will let you now exactly how long it takes to load the page,
and break down each and every resource that is also loaded in order to
render the page. This is also a great tool for determining what is
and what is not being cached.
I take the output of this and see if there is anything being loaded
that I'm not expecting. Every once in awhile I'll see where a user
might reference an image housed on an external site or server. This
can have serious consequences to load times.
I also look at the actual SharePoint page to see if there are any
hidden web parts loading list data. Most users accidentaly click
"Close" and not "Delete" so those web parts or list views are still
there. In some cases there could be significant data being loaded and
just not displayed.
Likewise I'll also take a look to see if any audiences are being used
since Audiences can be used to show/hide content.
尝试使用 hello world 托管应用程序，但在部署时遇到此错误，
Google Chrome could not load the webpage because myPortalapps-12812b1f934c6c.myPortal.apps.com took too long to respond
我可以 ping myPortalapps.myPortal.apps.com 但不能 ping myPortalapps-12812b1f934c6c.myPortal.apps.com
Sharepoint 网络应用程序 this forum post 帮助我解决了很多问题：
我也遇到了一些类似的问题When troubleshooting performance issues where more than one person/computer is impacted, the first place I like to start is by running a sniffer like Fiddler: http://www.fiddler2.com/fiddler2/version.asp
Fiddler will let you now exactly how long it takes to load the page, and break down each and every resource that is also loaded in order to render the page. This is also a great tool for determining what is and what is not being cached.
I take the output of this and see if there is anything being loaded that I'm not expecting. Every once in awhile I'll see where a user might reference an image housed on an external site or server. This can have serious consequences to load times.
I also look at the actual SharePoint page to see if there are any hidden web parts loading list data. Most users accidentaly click "Close" and not "Delete" so those web parts or list views are still there. In some cases there could be significant data being loaded and just not displayed.
Likewise I'll also take a look to see if any audiences are being used since Audiences can be used to show/hide content.