Stress and Performance Tool: FAQ
Topic Last Modified: 2011-02-22
Frequently Asked Questions
The following are some of the frequently asked questions about the Microsoft Lync Server 2010 Stress and Performance Tool.
Can I run LyncPerfTool.exe in production?
No. This tool will impact server performance and user experience.
I am logging on my users for the first time. Why are the servers running at such high load?
The first time the users log on, there are additional operations that occur. As a result, the performance on the SQL Server Back End Server will be degraded. We recommend that you run a short test that logs on all of the users, and then restart the clients before you measure results. We do not support more than 20 concurrent user sign ins per second, but this also depends on your SQL Server Back End hardware configuration.
My clients are running out of memory. What should I do?
If your clients are running out of memory, you need to reduce the number of users per computer.
My clients are at 100% CPU all the time. What should I do?
If your clients are running with very high CPU after all the users have logged on, you need to reduce the number of users per computer. High CPU spikes are acceptable, but if it is sustained you need to reduce the load.
Can I run the tool on the server itself?
No. This scenario is not supported and may fail due to a binary mismatch. Also, because the point is to measure resource consumption on the server, running the tool there would render the measurements meaningless.
Can I run LyncPerfTool.exe on a Virtual Server or on Microsoft Hyper-V Server 2008?
Currently only instant messaging (IM) and presence are supported on Microsoft Hyper-V Server 2008.
What does MPOP mean?
MPOP stands for multiple points of presence. It is meant to simulate the scenario where users are logged on to Lync 2010 from multiple machines. Note that in LyncPerfTool.exe, each endpoint follows the default profile (that is, the profile is not split between the two points of presence).
When I try to create contacts, I get an error saying “Enterprise X users in pool pool1.contoso.com not all accounted for. Users -- only contain -- actual users." What does this mean?
When Stressconfig.exe creates users, it populates attributes in Active Directory Domain Services (AD DS) and then Lync Server 2010 must replicate the new users to the databases. This can take several minutes when creating more than 10,000 users. Verify that the Standard Edition server is running or, in a Front End pool, that at least one Front End Server is running.
I started LyncPerfTool.exe but nothing is happening. What’s going on?
Check the Total Active Endpoints counter on the clients to see if the users are connecting. If no users can connect, verify your configuration. This usually occurs because the server name or the user prefix is incorrect. Note that external clients should specify the Access Proxy as the TargetServer value. Verify the port in the configuration file.
How do I know something is happening?
The various LyncPerfTool performance counters indicate whether or not users are connecting and performing actions. However, an easy way to check is to log on to one of the accounts by using Lync 2010 and performing the action you want.
My client is unable to scale up to the number of users I want but I am not running out of memory and I am not CPU bound. What could be causing this?
If the client was not restarted after you installed the tools, the MaxUserPort registry setting was not set in the registry. Restart the client and try again. (Note that this applies only to Windows Server 2003 operating system.
I have Microsoft Office Communications Server 2007 R2 Capacity Planning Tools installed. Is that OK?
No. There are interoperability issues and you must uninstall the Office Communications Server 2007 R2 tools.
Will the Stress and Performance tools set up the topology?
No. The tools can only create users, contacts, and distribution lists, and simulate user load.
What is the maximum number of users the tools support?
We have created up to 80,000 and run 30,000 users using these tools. We do not foresee more than 120,000 users being created and run, although the technical limitations allow for a higher number, mainly depending on client and server hardware available.