IM Messages number of messages received or sent Received/Sent for all sessions. Incoming/Outgoing Total number of incoming/outgoing Calls Attempted instant messaging calls attempted. Incoming/Outgoing number of incoming/outgoing instant Calls Established messaging calls established. Number of Total number of participants currently participants connected to conferences. Conference Schedule Total number of failures while trying to Failure schedule a conference. Join Conference Total number of failures while trying to Failure connect to a conference. Received 480 The number of 480s that clients receive This counter should (Temporarily remain near Unavailable) constant all users sign-in. During user you MAY see some 480s. This is expected behavior. Examples of Failed Performance Runs To better understand how your virtualized Office Communications Server Enterprise pool should function optimally, it is necessary to push the boundaries and observe how the system’s performance decreases. This document includes two examples to illustrate this point. 50,000 Internal When a test run that had 50,000 users signing-in to the Enterprise pool was performed, we observed that the %processor% performance counter on the back-end server reached 100% usage in approximately 40 minutes as shown in Figure 13. Figure 13 Back-end server CPU usage When we looked at the back-end virtual machine properties on Hyper-V, we saw that the “Virtual Machine reserve (percentage)” value was set to 0. By increasing this value to 100, we observed that it took 2 hours for the back-end server's CPU usage to reach 100%. After the back-end server's CPU usage reached 100%, the rate of endpoints being ended rapidly increased. This resulted in users not being able to sign-in to the Enterprise pool as shown in Figure 14.
IM Messages Received/Sent number of messages received or sent for all sessions. Incoming/Outgoing Calls Attempted Total number of incoming/outgoing instant messaging calls attempted. Incoming/Outgoing Calls Established number of incoming/outgoing instant messaging calls established. Number of participants Total number of participants currently connected to conferences. Conference Schedule Failure Total number of failures while trying to schedule a conference. Join Conference Failure Total number of failures while trying to connect to a conference. Received 480 (Temporarily Unavailable) The number of 480s that clients receive This counter should remain near constant all users sign-in. During user you MAY see some 480s. This is expected behavior. Examples of Failed Performance Runs To better understand how your virtualized Office Communications Server Enterprise pool should function optimally, it is necessary to push the boundaries and observe how the system’s performance decreases. This document includes two examples to illustrate this point. 50,000 Internal When a test run that had 50,000 users signing-in to the Enterprise pool was performed, we observed that the %processor% performance counter on the back-end server reached 100% usage in approximately 40 minutes as shown in Figure 13. Figure 13 Back-end server CPU usage When we looked at the back-end virtual machine properties on Hyper-V, we saw that the “Virtual Machine reserve (percentage)” value was set to 0. By increasing this value to 100, we observed that it took 2 hours for the back-end server's CPU usage to reach 100%. After the back-end server's CPU usage reached 100%, the rate of endpoints being ended rapidly increased. This resulted in users not being able to sign-in to the Enterprise pool as shown in Figure 14.
OCS2007R2_with_Hyper-V.docx