Microsoft releases a performance document on RD Connection Broker in Windows Server 2012.
“…In Windows Server 2012, RD Connection Broker provides the following functionality:
- Allows users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops.
- Enables you to evenly distribute the load among RD Session Host servers in a session collection, or pooled virtual desktops in a pooled virtual desktop collection.
- Provides access to virtual desktops in a virtual desktop collection.
In Windows Server 2012, RD Connection Broker functionality is extended so that you can easily create collections. Connection routing and load-balancing capabilities are also improved. This document presents performance and scalability testing results for RD Connection Broker. It describes the most relevant factors that influence the performance of the component…”
The document also contains some recommendations regarding the RD Connection Broker role:
“…Recommendations for the RD Connection Broker setup:
· Highly Available RD Connection Broker. Use High Availability configuration for the RD Connection Broker. High availability provides increased reliability and availability at the same time, allowing the processing of a larger number of concurrent connections.
· Hardware for RD Connection Broker. We recommend server hardware with at least 4 cores and 4 GB of RAM. In the testing environment HP Z400 servers were used for benchmarking.
· SQL Server configuration. Quad-core machine with at least 4 GB of RAM, Standard or Enterprise SQL Server ver. 2008 R8 and newer…”
Source and download: