限制ASP.NET 4.5中WebSocket的性能因素? [英] Limiting performance factors of WebSocket in ASP.NET 4.5?
问题描述
MSDN文档似乎没有很好地覆盖ASP5对HTML5的支持 WebSockets协议!
MSDN documentation doesn't seem to have good coverage on ASP.net 4.5 support of HTML5 WebSockets protocol!
这就是我要找的:
- 服务器/应用程序/ cpu支持多少个活动连接?
- 是否有可以设置/获取的最大传入连接数?
- 无论数据传输如何,每个应用程序的最佳套接字数是多少在套接字上?
更新:
Requests from flash RTMP sockets (an alternative to websocket) could be well configured on Adobe Media Server application server. Isn't any sort of configurations for number of requests, ideal time, size of chunks, ... for ASP.net inside application or IIS 8 configuration?
推荐答案
对于任何可能感兴趣的人:
To whomever may be interested:
- 超过100k的WebSocket连接可以连接到单个服务器
运行ASP.NET 4.5 -
WebSocket连接由HTTP
握手启动,因此部分适用于HTTP请求的IIS限制
也适用于WebSockets。 IIS配置中的
appConcurrentRequestLimit
可用于设置每个应用程序的最大并发请求数:
- Over 100k WebSocket connections can be made to a single server running ASP.NET 4.5
WebSocket connections are initiated by a HTTP handshake, hence some of the IIS throttles that apply to HTTP requests will also apply to WebSockets.
appConcurrentRequestLimit
in the IIS Configuration can be used to set the maximum concurrent requests per application:
<serverRuntime appConcurrentRequestLimit="250000" />
ASP.net 4 Web的最大并发连接数可以使用 ApplicationPool的maxConcurrentRequestsPerCPU 属性设置应用程序:
<system.web>
<applicationPool maxConcurrentRequestsPerCPU="20000" />
</system.web>
当总连接数超过$ b时$ b maxConcurrentRequestsPerCPU
设置,ASP.NET将使用队列启动限制请求。要控制队列的大小,你可以
调整 machine.config requestQueueLimit :
When the total amount of connections exceed the
maxConcurrentRequestsPerCPU
setting, ASP.NET will start throttling requests using a queue. To control the size of the queue, you can
tweak the machine.config requestQueueLimit:
<processModel autoConfig="false" requestQueueLimit="250000" />
在$ b时应考虑以下性能指标$ b进行并发测试并调整最佳设置
详细说明:
The following performance counters should be considered while conducting concurrency testing and adjusting the optimum settings detailed above:
- 所有堆中的NET CLR内存#bytes
- ASP.NET \请求当前 - 排队 - 拒绝
- 处理器信息\Processor Time
- TCP / IP已建立连接
- Web服务\当前连接 - 最大连接数
- .NET CLR LocksAndThreads \#当前逻辑线程数 - 当前物理线程数#
- NET CLR Memory #bytes in all Heaps
- ASP.NET\Requests Current - Queued - Rejected
- Processor Information\Processor Time
- TCP/IP Connections Established
- Web Service\Current Connections - Maximum Connections
- .NET CLR LocksAndThreads\ # of current logical Threads - # of current physical Threads
这篇关于限制ASP.NET 4.5中WebSocket的性能因素?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!