Azure文件服务与Azure VM作为文件服务器 [英] Azure File Service vs Azure VM as a File Server

问题描述

全部

我正在比较两种情况下文件访问的性能.

I am comparing the performance of File Access in 2 scenarios.

1.文件位于Azure文件服务上-可从Azure VM访问.

1. Files are on Azure File Service - accessing from an Azure VM.

2.文件位于Azure VM上-可以从同一子网上的其他Azure VM访问.

2. Files are on Azure VM - accessing from a different Azure VM on the same subnet.

我注意到情况2比情况1快30％.这是预期的吗?在相同的资源组和相同的位置(美国中南部)，使用相同的参数创建了VM和文件服务.

I notice that case 2 is about 30% faster than case 1. Is this expected? Both VMs and the file service were created with the same parameters, in the same resource group and in the same location (SouthCentral US).

这是预期的吗?我可以调整任何参数以使文件服务与VM一样快吗?

Is this expected? Are there any parameters I can tweak to make my file service as fast as my VM?

谢谢！

VJ

推荐答案

这是因为您已经创建了供自己使用的VM. (就像租约一样)

This is because you have created a VM for your own use and you are using. (Like a lease)

但是在第一种情况下，您的文件被部署在支持的逻辑服务器上，这是我们所不知道的.现在，当您尝试从文件服务器检索文件时，它会通过RESTAPI进行查询，并使用SMB协议.

But in scenario first your file is deployed on logical server in backed, which we do not know. Now when you try to retrieve file from file server then in backed it queried through RESTAPIs and worked on SMB protocol. 

另一方面，当您从VM检索文件时，RESTAPI不存在，因为它是您自己的VM.

On the other hand when you retrieve your file from VM, RESTAPIs are not there since it is your own VM.

进一步，您可以

希望这会有所帮助:)

Hope this helps :)  

这篇关于Azure文件服务与Azure VM作为文件服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！