|
|
Windows Media Load Simulator must be installed on a client machine and is intended to test the capacity of the Windows Media Unicast Service on a Windows Media server. The load simulator simulates a high client demand by initiating a large number of client requests for streams to potentially overwhelm the system and network resources of your site. Each instance of Windows Media Load Simulator can request streams for up to 200 simulated clients. To create an even larger demand on the Windows Media server, you can run multiple instances of Windows Media Load Simulator on a single client machine or on multiple client machines against the same Windows Media server. For example, is you want to determine if your Windows Media server can handle 1,000 client requests for unicast content, you can run five instances of Windows Media Load Simulator, each configured to simulate 200 clients, on one client machine. Or you can run a single instance of Windows Media Load Simulator, each configured to simulate 200 clients, on five client machines
Windows Media Load Simulator also allows you to create user names and passwords for the simulated clients. The Windows Media server must process this information and authenticate each user, which consumes even more server resources. Windows Media Load Simulator supports authentication using Basic User Authentication and Windows NTLM on the Windows Media server. For more information, see To set server authentication.
Note Windows Media Load Simulator only initiates unicast connections to the server. Multicast connections are not supported because a client does not connect to the server to view a multicast.