在Windows Azure存储（BLOB，表，队列），用于从Windows Azure的角色访问进行了优化？ [英] Is Windows Azure Storage (Blob, Table, Queue) optimized for access from Windows Azure Roles?
问题描述
目前，我正在寻找Windows Azure中承载的 ElasticSearch 实施。加载应用程序并运行它在Java并不难。
I'm currently looking at Windows Azure to host an ElasticSearch implementation. Loading the application and running it under Java is not that difficult.
目前，<一个href="http://elasticsearch-users.115913.n3.nabble.com/Cloud-plugin-for-0-15-0-using-Azure-blob-storage-tp2604241p2605520.html">ElasticSearch只支持Amazon的S3 ，当涉及到云存储。
Currently, ElasticSearch only supports Amazon's S3 when it comes to cloud storage.
这样一来，我做了一个请求添加支持的Azure Blob存储在ElasticSearch 。
As a result, I've made a request to add support for Azure Blob Storage in ElasticSearch.
之后我提出的要求，它发生在我，虽然我可以在Azure中托管ElasticSearch，我可以创造一个亚马逊S3 帐户，然后在Azure中运行的实例连接到S3账户存储。
Right after I made the request, it occured to me that while I can host ElasticSearch in Azure, I can create an Amazon S3 account and then have the instance running in Azure connect to the S3 account for storage.
但是，我有关于这两者之间的速度的担忧。虽然我相信这两个Azure存储和Amazon的S3都为真快的速度，我有一种挥之不去的感觉，存储系统进行了优化的的真正的从各自的计算集群进行访问时进行了优化。
However, I do have concerns about the speed between the two. While I am sure both Azure Storage and Amazon's S3 are both optimized for really fast speeds, I have a nagging feeling that storage systems are really optimized when accessed from their respective computing clusters.
这是说，有没有在这个任何明确的信息？这是有道理的，但是我正在寻找具体的确认或否认。
That said, is there any definitive information on this? It makes sense, but I'm looking for specific confirmation or denial.
推荐答案
这不是这么多的Azure角色的Azure存储API的优化的问题，只是身体在同一地点和啤酒花的网络距离/数问题。你可以（也应该）指定您的Azure存储服务驻留在同一数据中心将使用该存储服务Azure的角色。
It's not so much a matter of optimization of the Azure storage API for Azure Roles, but simply a matter of physical co-location and network distance / number of hops. You can (and should) specify that your Azure storage service resides in the same data center as the Azure roles that will be using that storage service.
您可以期待的网络带宽是最大和延迟之间的Azure角色和居住在同一个数据中心的Azure存储是最低的。带宽会降低，而且等待时间，当你的Azure角色连接到任何自己的数据中心之外的更高的 - 是，Azure存储在另一个数据中心或Amazon S3存储在另一个数据中心
You can expect network bandwidth to be greatest and latency to be lowest between an Azure role and an Azure storage residing in the same data center. Bandwidth will be lower and latency higher when your Azure role connects to anything outside of its own data center - be that Azure storage in another data center, or Amazon S3 storage in another data center.
另外的表现，也请记住，你付出的进出在Azure数据中心为您服务的所有的数据流量。有了Amazon S3上或在其他的Azure数据中心的Azure角色访问的数据将采取咬了你的带宽配额，而同一数据中心内访问Azure存储成本你一无所有，不管你自己的角色和你之间有多大的流量使用Azure存储。
Besides performance, also keep in mind that you pay for all data traffic in and out of the Azure data center for your services. Having your Azure role accessing data on Amazon S3 or in another Azure data center will take a bite out of your bandwidth quota, whereas accessing Azure storage within the same data center costs you nothing, no matter how much traffic you use between your role and your Azure storage.
这篇关于在Windows Azure存储（BLOB，表，队列），用于从Windows Azure的角色访问进行了优化？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
