|Charles Sterling wrote that Microsoft had published a new white paper on Team System Web Access Scalability Limits.|
According to Charles:
"This article explains the scalability limits of Team System Web Access and provides three workarounds to improve the total number of concurrent users that Web Access can support including a neat batch command that will recycle IIS and clean up the TSWA cache."
So I had to check it out and after digging it for a while, here are the top notes I derived:
- It is not recommended to have more than 100 concurrent users using a single Web Access instance.
- Each Web Access user uses a substantial amount of memory to store work item tracking objects in an ASP.NET session.
- On 32 bit operating systems, a single process (such as Web Access) can use up to 2 GB memory, which means the total number of concurrent users will be limited to approximately 100 if each user session consumes about 20 MB memory.
- A large number of concurrent users might cause lock contention issues with the metadata cache files.
The White Paper also contains information about the Load Tests that were executed against the Web Access and workarounds.
You can download it from here.