大网数据广告活动
网络与域名解析

Upload Best Practices

· 52CE 我爱测

Highloads may cause various server timeout conditions, which may in turn increase the load when the client retries.

Highloads may cause various server timeout conditions, which may in turn increase the load when the client retries. Also, a large number of outstanding connections will consume more server resources and make the situation worse. On top of that, if backend app is not written to handle high load conditions, it may crash or mal-behave. The app shall perform the following steps to limit the load on the backend.

If the server application is not written to handle high volumes, timeout conditions may occur, which may in turn increase the load when the client retries. Also, a large number of outstanding connections will consume more server resources.

When testing your server application, test with highest load possible. You should use multiple client machines, each with several concurrent, foreground BITS jobs, and measure the maximum throughput at the backend. If you cannot measure the throughput, you will have to estimate the throughput.

The server application should reside on a different URL from the upload URL (see the BITS IIS property, BITSServerNotificationURL).

It is good practice to limit the load on the application server based on proven throughput values. You should use the IIS properties, MaxBandwidth and MaxConnections, to limit the load on the application server.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。