Azure的Web角色和SQL Azure和应用程序性能之间的延迟 [英] Latency between Azure Web Role and SQL Azure and Application performance

问题描述

Azure的Web角色和的Sql Azure的延迟

喜只知道有在网络工作者的作用和之间的延迟和超时的 SQL Azure的后，事件在某次超时（这一个是不是随机的有频繁），100坪的40％没有0毫秒超时

Hi Just to know that there is a latency and timeout between the web worker role and SQL Azure , Event a Timeout at some times (These a are not random having frequently ) 40% of 100 pings does not have 0ms timeout

如果网络工作者的角色和SQL Azure在同一数据中心为什么会出现超时，因为他们使用的是他们的内部网络通信

if Web worker role and SQL Azure in the same data center WHY there is a timeout as they are communicating using their internal network

请参照附截图：

应用程序有一个神秘的表现跌宕起伏。如果可能由于各种原因，但我需要知道的是，在做延迟和超时论文统计影响Web应用性能？

Application which runs on this web worker role has a mysteries performance ups and downs .. if may be due to various reasons but what i need to know is that does theses statistics on latency and timeout affects web application performance ?.

谢谢，

推荐答案

首先，你需要知道，Windows Azure的SQL数据库是作为服务提供的多租户，高密度的RDBMS。这意味着，单个服务器所使用的可能是数百家客户。

First of all, you need to know that Windows Azure SQL Database is a multi-tenant, high-density RDBMS offered as a service. That means, that a single server is used by possibly hundreds of customers.

我也建议你去了解 SLA的服务 的Windows Azure SQL数据库尤其是。没有人具有以往权利要求，将有0毫秒的延迟。也有这样的事情<一个href=\"http://windowsazurecat.com/2010/10/best-practices-for-handling-transient-conditions-in-sql-azure-client-applications/\"相对=nofollow>瞬态条件Windows Azure中的SQL数据库。

I also suggest that you get to know the SLA for the services, Windows Azure SQL Database in particular. Noone has ever claim that there will be 0ms latency. There is also such thing as "Transient Conditions" in WIndows Azure SQL Database.

一个很好的建议阅读是<一个href=\"http://social.technet.microsoft.com/wiki/contents/articles/3507.windows-azure-sql-database-performance-and-elasticity-guide.aspx\"相对=nofollow>的Windows Azure SQL数据库性能和elasticiy指南。

A good suggested reading is the Windows Azure SQL Database Performance and elasticiy guide.

对于Web应用程序的性能，读取性能和弹性指南后，我不认为在一段时间发生一次的200ms的是核心瓶颈。

As for web application performance, after reading the Performance and elasticity guide, I don't think the 200ms that happens once in a while are the core bottleneck.

更新第一个注释后

您将永远在一个共享的环境跌宕起伏。你也应该想到查询执行时间来改变上下。这是在那种环境下，你必须设计并住在一起的东西不可避免的。有没有魔术棒在这里，有没有你的专用服务器（我们）在Windows Azure中的SQL数据库的情况。如果你认为你的应用程序需要更可靠的SQL Server服务，您可以尝试在Windows Azure虚拟机和自己带来了一个SQL Server群集。我想（这只是一个猜测），你的云服务和虚拟机之间的通信，因为一切都在相同的可用性组，将更predictable。

You will always have ups and downs in a shared environment. You should also expect query execution times to change up and down. This is unavoidable in that kind of environment and something you have to design for and live with. There is no magic wand here, and there is no dedicated server for you (for us) in the case of Windows Azure SQL Database. If you think that you app needs more reliable SQL Server services, you might try the Windows Azure Virtual Machines and bring up a SQL Server cluster by yourself. I guess ( and this is only a guess) that the communication between your cloud service and your VMs, given everything is in the same availability set, will be more predictable.

更新后的第二和第三个意见：

嗯，是的，你可能有许可证的问题（我在许可的专家）。是门票你已经打开了跌宕起伏？如果是这样，你可以尝试升级它（不知道怎么回事，但你有你的票号，还必须有一个指定的工程师，买不到票的电子邮件 - 回复到所有的电子邮件） 。此外，当您创建的票一定有一个小问卷，以反映您的问题对业务的影响。然后通常响应时间必须被分配给票。如果支持，没有在该时间内回来给你，你绝对可以升级它。

Well, yes, you might have licensing issues (I'm the expert on licensing). Is the ticket you have opened for the ups and downs? If so, you may try to escalate it (don't know how, but you have your ticket ID, you must also have an assigned engineer and an e-mail about the ticket - reply-to-all to that e-mail). Also, when you created the ticket there must have been a small questionnaire to reflect the business impact of your issue. Then a usual response time must have been assigned to the ticket. If the support has not come back to you within that time, you can definitely escalate it.

更新

有趣的观察，我是在你的所有屏幕截图，只有第一个数据包被延迟，那么每个连续有0延迟。在所有的样品您提供。如果您遇到这种情况10出10次，那么你绝对不与延迟的问题。我会建议你使用-t选项，在常平发送超过4包，观察。我建议在突破约100包，然后观察结果。我不会考虑到4包样品，其中只有第一个具有延迟时间的任何业绩回顾。

Interesting observation that I have is that in all your screenshots only the first packet is delayed, then every consecutive has 0 latency. In all the samples you are providing. If this is your case 10 out of 10 times, then you are definitely not having any issues with latency. I will suggest that you use the "-t" option in the regular ping to send more than 4 packets and observe. I suggest breaking at around 100 packets, and then observe the results. I would not take into account 4 packet samples, where only first one has latency for any performance reviewing.

这篇关于Azure的Web角色和SQL Azure和应用程序性能之间的延迟的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！