User models in Lync Server 2013

 

Topic Last Modified: 2013-10-07

The user models described here provide the basis for the capacity planning measurements and recommendations described in Capacity planning for Lync Server 2013 using the user models.

Lync Server 2013 User Models

The following table describes the user model for registration, contacts, instant messaging (IM), and presence for Lync Server 2013.

Environment and Registration User Model

Category	Description
Deployment size and distribution	We model a large deployment with three central sites, with one Front End pool per site.
Percentage of Active Directory users	We assume that 70% of all Active Directory users in the organization are enabled for Lync Server. 80% of those enabled users are logged on to Lync Server each day (80% concurrency). The concurrent users are the basis for the numbers in the rest of this section.
Active Directory changes	We assume that 0.5% of total users are created and enabled for Lync in Active Directory each week, and that 0.5% of total users are disabled from Active Directory and from Lync each week. 5% of users have at least one Active Directory attribute changed each week.
Active Directory distribution groups	We assume that the number of Active Directory distribution groups in the organization is equal to three times the number of all users in Active Directory. The distribution groups have the following sizes: 64% have 2-30 users 13% have 31-50 users 10% have 51-100 users 13% have 101-500 users
Voice over IP (VoIP) users	60% of Lync Server users are enabled for unified communications (UC) (that is, their phone numbers are owned by Lync Server).
Registered client distribution	65% of clients run Lync 2013 software, including Lync and Lync Phone Edition. 30% of clients running client software from a previous version of Lync. 5% of clients using Lync Web App. If mobility is enabled, we assume that 40% of users are using mobility concurrently with the other previously cited registered client options. In this case the client multiple point of presence (MPOP) ratio is 1:1.9. If mobility is disabled, the MPOP ratio is 1:1.5.
Remote user distribution	70% of users connecting internally. 30% of users connecting through an Edge Server and a Director.
Contact distribution	The maximum number of contacts a user has is 1,000. Less than 1% of users have 1,000 contacts. Less than 25% of users have 100 or more contacts. Average of 80 contacts for users with public cloud connectivity. Of these users: 50% of the contacts are within the organization. 10% of those users are remote users, connecting from outside the firewall. 40% of the contacts are public cloud users (such as users of AOL, Yahoo!, MSN, or Google Talk). 10% of the contacts are from federated partners. Important As of September 1st, 2012, the Microsoft Lync Public IM Connectivity User Subscription License (“PIC USL”) is no longer available for purchase for new or renewing agreements. Customers with active licenses will be able to continue to federate with Yahoo! Messenger until the service shut down date. An end of life date of June 2014 for AOL and Yahoo! has been announced. For details, see Support for public instant messenger connectivity in Lync Server 2013. The PIC USL is a per-user per-month subscription license that is required for Lync Server or Office Communications Server to federate with Yahoo! Messenger. Microsoft’s ability to provide this service has been contingent upon support from Yahoo!, the underlying agreement for which is winding down. More than ever, Lync is a powerful tool for connecting across organizations and with individuals around the world. Federation with Windows Live Messenger requires no additional user/device licenses beyond the Lync Standard CAL. Skype federation will be added to this list, enabling Lync users to reach hundreds of millions of people with IM and voice. Average of 50 contacts for users without public cloud connectivity. Of these users: 80% of the contacts are within the organization. 10% of those users are remote users, connecting from outside the firewall. 20% of the contacts are from federated partners. Each user has 1 distribution group in their contact list. For performance testing, we assume that distribution groups are always expanded. 25% of a user’s contacts use XMPP.
Session time	The average user logon session lasts 12 hours. All users log on within 120 minutes of the start of the session.

IM and Presence User Model

Category	Description
Peer-to-peer IM sessions	Each user averages six peer-to-peer IM sessions per day. 10 instant messages per session. Each message is matched by two SIP INFO messages and 2 SIP 200 OK messages (for the status indicators such as “<Name> is Typing”)
Presence polling	Overall, we assume presence polling at an average of 60 polls per user per hour. For each user, assume an average of: One poll per day of the presence of users in the user’s organization tab (but not Contacts list). Average number of non-contacts in the user’s organization tab is 15 users. Two contact card viewing operations per day. One presence poll every time the user clicks another user to start a conversation, estimated at once per hour. Six user searches per hour. Every time a search is performed, a batch poll is sent for everyone in the search result list. We assume the average size of search results is 20. If the search results stay on screen, the batch poll is refreshed every 5 minutes; we assume that there will be two such refreshes per hour. When the user opens or previews an email in Outlook, a poll of the presence of users in the To: and CC: fields of the email, estimated at five emails per hour and four users per email.
Presence subscriptions	When one user adds another as a contact, the first user is subscribing to five categories of information about the second user. Updates of these categories of information are automatically sent to the first user. For each client, a single batch subscription request is sent to obtain the presence state of an average of 40 contacts, with an additional 40 dialogs to obtain presence for federated contacts. Presence for members of an expanded distribution group is found through persistent presence subscriptions, not polling, and is modeled as 1 expansion per user for each 2 hours. Short subscriptions happen when a user logs in, there is a batch subscription for all the user’s contacts, and then the user soon logs off. We assume 6 short subscriptions per user per hour, where each subscription lasts 10 minutes.
Presence Publication	Presence state is published at an average of 4 publications per user per hour, with a maximum 6 per user per hour.
Presence Document Size	The average size of a complete presence document is assumed to be 4K, with a maximum of 25K.

The following table describes the user model for address book use.

Address Book Usage User Model

Address Book search mode	Usage
Address Book Web Query only (all queries performed by Address Book Web Query service)	Four prefix queries per user per day. 60 exact search queries per user per day. 40% of those are batched, with an average of 20 contacts per query. The other 60% of the queries are for a single contact. 25 photo queries per user per day. 24 are for a single photo, the other is a batch query with an average of 20 contacts. One total organization search query per user per day.
Mixed mode, both address book file and web queries used. This is the default mode.	Only two types of queries go to the network, the photo and total organizational search queries. 25 photo queries per user per day. 24 are for a single photo, the other is a batch query with an average of 20 contacts. One total organization search query per user per day.

The following table describes the conferencing model.

Conferencing Model

Category	Description
Scheduled meetings versus "Meet now" meetings	60% scheduled, 40% unscheduled. Of the scheduled meetings, we assume that 80% are assigned conferences, which are occurences of recurring conferences; 10% are one-time open meetings; 8% are one-time anonymous meetings, and 2% are one-time closed meetings.
Conferencing client distribution	For scheduled meetings: 65% of conferencing users use Lync 2013. 5% of conferencing users use Microsoft Lync Web App. 30% of conferencing users use earlier clients, including Microsoft Lync 2010, Office Communicator 2007 R2, Office Communicator 2007, and Microsoft Office Communicator Web Access (2007 release). For unscheduled meetings: 70% of conferencing users use Lync 2013. 30% of conferencing users use earlier clients, including Microsoft Lync 2010, Office Communicator 2007 R2, Office Communicator 2007, and Microsoft Office Communicator Web Access (2007 release).
Meeting concurrency	5% of users will be in conferences during working hours. Thus, in an 80,000-user pool, as many as 4,000 users might be in conferences at any one time.
Meeting audio distribution	40% mixed VoIP audio and dial-in conferencing, with a 3:1 ratio of VoIP users to dial-in users. 35% VoIP audio only. 15% dial-in conferencing audio only. 10% no audio (IM-only conferences, with an average of five messages sent per user).
Media mix for conferences	75% of conferences are web conferences, which include audio plus some other collaboration modalities. For these conferences, the other collaboration methods are as follows: Note These numbers add up to more than 100% because one conference can have multiple collaboration methods. 50% add application sharing. We assume one users sends data at a peak of 1.1 MB per second. 50% add instant messaging (with an average of 2 messages per user). 20% add data collaboration, including PowerPoint or whiteboard In these, an average of 2 PowerPoint files presented per conference, with an average PowerPoint file size of 10 MB (without embedded video) or 30 MB (with embedded video). Average of 20 annotations per whiteboard. 20% add video. Of these users, 70% are in conferences enabled for multiview video, where each user receives 2-3 video streams. 15% add shared notes.
Meeting participant distribution	50% internal, authenticated users. 25% remote access, authenticated users. 15% anonymous users. 10% federated users.
Meeting join distribution	Users are simulated as joining the meeting within the first 5 minutes.

In regular Front End pools, Lync Server 2013 has a maximum supported meeting size of 250 users. Each pool can host one 250-user meeting at a time. While this large meeting is occurring, the pool can also host other smaller conferences. Additionally, you can support meetings of up to 1000 users by setting up a dedicated pool to host these meetings. For details, see Support for large meetings in Lync Server 2013.

Conferences were simulated as follows:

• 85% of conferences had four participants.

• 10% of conferences had six participants.

• 5% of conferences had 11 participants.

• One large conference of 250 users.

The following table provides details about the user model for conferences involving dial-in users.

Dial-In Conferencing User Model

Category	Description
Authenticated/anonymous	70% of callers join as anonymous and are prompted for a recorded name. 30% join as authenticated users.
Call duration and music on hold	Average call duration without music on hold: 50 seconds. 50% of call-in users hear music on hold, for an average of 5 minutes.
Dual-tone multifrequency (DTMF)	15% of conferences that are dial-in only have phone leaders. 10% of mixed conferences that include dial-in users also have phone leaders. 20% of phone leaders use 2 DTMF commands per conference.
Announcement languages	Simulations use English as the announcement language.

The following table provides details about the user model for conference lobbies.

Conference Lobby User Model

Category	Description
Number of users in lobby	5% of dial-in users go through the lobby, and 25% of other users go through the lobby
Admitting from lobby	In simulations, all users were admitted by the presenter before client timeout.

The following table describes the user model for other peer-to-peer sessions.

Peer-to-Peer Sessions User Model

Category	Description
Application sharing	Each user participates in 5 peer-to-peer application sharing sessions per month, for an average of 0.25 sessions per day.
File transfer	Each user participates in 1 peer-to-peer file transfer session per month (as part of an IM session), for an average of 0.05 sessions per day. The average session file size transferred is 1 MB.

The following table describes the user model for policies.

Policies User Model

Category	Description
Conferencing, Presence, and Archiving Policies	We assume that there is one global policy, 10 tag conferencing policies, 4 Archiving policies, and 10 tag presence policies.
Voice Policy	We assume that there is one global policy and 2 tag policies per site. 100% of sites have a site policy, and 30% of users have a per-user policy assigned. We assume one dial plan per site and two routes per site.

Busy Hour

For peer-to-peer sessions, peak load is calculated using busy hour call attempts (BHCA). This voice industry term assumes that 50% of all calls for the day will be completed in 20% of the time. It is calculated using the following formula:

BHCA=(total calls * 0.5) / 1.6

Performance testing simulated busy hour by running VoIP and other peer-to-peer sessions at a busy hour load for at least 1.6 hours per day.

Conferencing peak load assumes that 75% of all conferences for an eight-hour day happen in 4 peak time hours. Those peak hours have 1.5 times the average conferencing load.

Enterprise Voice to PSTN Calls

The following assumptions apply to Enterprise Voice calls:

• 50% of users are enabled for Enterprise Voice, and 60% of these users are enabled for PSTN calling.

• Each of these users enabled for PSTN calling makes 4 PSTN calls during the busy hour. Each call duration is 3 minutes.

• 65% of these PSTN voice calls use media bypass.

Mobility

40% of registered users are assumed to be enabled for Mobility. For each user that has mobility enabled, we assume that the activity of the mobile client is additive to that of the other MPOP instances for that user, with the exception of conferencing interactions, for which the mobility client is just another client type that can be used to participate in conferences.

Persistent Chat

We assume that 25% of registered users will be involved in Persistent chat sessions, with the following characteristics:

• An average of 1.5 chat rooms per user

• Each chat room results in 12 polling requests per hour, targeting an average of 10 users each

Response Group and Call Park

We assume that 0.15% of registered users belong to response groups. We assume that 0.02% of registered users have parked calls at any given point of time.