ServicePointManager.DefaultConnectionLimit在工作者角色 [英] ServicePointManager.DefaultConnectionLimit in Worker Role

问题描述

刚学有关的Windows Azure的时刻。

Just learning about Windows Azure at the moment.

我在看一些样本，并在
的辅助角色我看到的OnStart事件

I'm looking at a few samples and in the OnStart Event of a worker role I see

ServicePointManager.DefaultConnectionLimit = 5;

ServicePointManager.DefaultConnectionLimit = 5;

我不明白这样的相关性。

I do not understand the relevance of this.

在您的辅助角色，您可以设置实例的数量，以便肯定这限制条目的数量？

In your worker role, you can set the number of instances so surely this limits the number of entries?

对不起，我糊涂了。

推荐答案

我们打类似这样我们的团队有问题。默认情况下，每个域的传出连接的默认数量默认设置为2。这限制了可以有，可引起执行问题的并行连接的数目。我想看看下面的博客，其进入对这个问题的一些细节。

We hit a problem similar to this on our team. By default, the default number of outgoing connections per domain is set to 2 by default. This limits the number of concurrent connections that you can have and can cause perform issues. I'd take a look at the blog below, which goes into some detail on the problem.

<一个href=\"http://blogs.msdn.com/b/jpsanders/archive/2009/05/20/understanding-maxservicepointidletime-and-defaultconnectionlimit.aspx\">http://blogs.msdn.com/b/jpsanders/archive/2009/05/20/understanding-maxservicepointidletime-and-defaultconnectionlimit.aspx

在调节实例的数量，而可以扩展被天青的内部运行的实例的数量，只是向外扩展上的单个实例不会解决瓶颈方面。

In terms of adjusting the number of instances, while can scale out the number of instances that are running inside of Azure, simply scaling out will not address bottlenecks on a single instance.

这篇关于ServicePointManager.DefaultConnectionLimit在工作者角色的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！