Azure 存储模拟器性能问题
我正在尝试将 Windows 服务器设置为我的本地服务器。我能够克服连接问题（计算机模拟器仅侦听 127.0.0.1），但现在我面临一个新的、更困难的问题。
写入本地 BLOB 存储需要很长时间。
我编写了一个简单的“hello world”ASP.NET Web 角色，它将随机文件写入队列和 BLOB。 Web 角色与存储模拟器在同一台计算机上运行。写入队列相当快，但 BLOB 则完全不同。
写入 BLOB 使我的网络角色运行速度慢了 50 倍（！）。
对云存储使用完全相同的代码使其运行速度更快。这告诉我问题肯定在于使用本地存储模拟器。
有谁知道如何提高存储模拟器的性能？
谢谢您的宝贵时间， 埃拉德
I am trying to setup a windows server to be my on-premises server. I was able to overcome the connection issues (the Computer Emulator only listens to 127.0.0.1), and now I face a new, more difficult problem.
Writing to the local BLOB storage takes a very long time.
I wrote a simple "hello world" ASP.NET Web Role that writes a random file to a Queue and to a BLOB. The web role runs on the same machine with the storage emulator. Writing to the Queue is fairly fast, but the BLOB is a completely different story.
Writing to the BLOB made my web role work 50 times slower(!).
Using the exact same code against the cloud storage made it work much faster. This tells me that the problem definitely lies in using the local storage emulator.
Does anyone have an idea how to boost the storage emulator's performance?
Thank you for your time,
Elad
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
恭喜您让服务器在本地工作，这对我来说总是显得太辛苦了。由于您已经付出了所有这些努力，我认为这是为了避免在开发或测试时为云中的计算实例付费。
我提前道歉，我实际上不会回答您有关如何加快开发存储速度的问题。这是因为开发存储和我真的合不来。它与您从实际云存储中获得的结果非常接近，但如果您针对开发存储进行开发然后切换到真实的存储，则差异可能会很大，足以导致问题。
简而言之，我想说，即使您在本地运行，也只需忽略开发存储并直接连接到云。这会产生相关的成本，但根据我的经验，存储成本确实很小。每月 5 美元就足够了。
Congratulations on getting the server to work on premises, that always seemed like too much hard work to me. As you've gone to all of that effort I'm presuming that it's to avoid paying for compute instances in the cloud while you develop or test.
I apologise in advance that I'm not actually going to answer your question about how to speed up development storage. This is because development storage and I really just don't get along. It's pretty close to what you get from actual cloud storage, but the differences can be significant enough to cause problems if you develop against development storage then switch to the real thing.
In short, I'd say just ignore dev storage and connect straight to the cloud even though you're running locally. This will have a cost associated with it, but in my experience the costs for storage are really quite small. $5 per month will go a long way.