We haven't done a formal load testing yet. But we have conducted training with 10 - 15 users and would experience performance sometimes people just getting kicked out. At the time though we were still finagling with server configuration settings for threads, cache and java heap. During training too what seemed to impact performance more was the browser and version, and workstation memory. For a web app, TES 6.1 uses a LOT of memory so there were some suggested tweaks that had to be done on some machines. We have more consistent performance on IE 9 (than IE 10), and Firefox 18+ was faster.
I have installed Jconsole and am planning to conduct load testing sometime this month where i could monitor server resource from Jconsole to get an idea where bog down really is.
There is a TES 6.1 presentation doc that sort of outlines approx sizing based on concurrent users - we fit in the 10 -20 concurrent users given that our CM has 12GB RAM (allocated 10GB to TES) and 4 core. So hopefully with two CMs we can have upto 40. We are open to adding more mem if needed. So what tools do you use for Load testing? Also I wonder if it was possible to automate Load Testing like with Jmeter or something. For now we just plan on getting 20 users together to perform set functions at the same time and measure that with 1 CM up and me looking in Jconsole.
I also notice the multiple connections, even see myself twice even when I only have 1 browser session. Not having had a chance to dig to deeply i was chalking it up to maybe that I didn't exit properly last time so that it has to wait 30 minuts to totally clear me (with time to live setting) out but haven't really tested formally. I will see about adding that to my testing. I would also think it would impact system in that some folks may cause the number of concurrent connections allowed to be exceeded if you have too many of these lying around but since they are not doing anything perhaps not performance as much? It will be good to confirm though that a single web session really only takes 1 connection and won't potentially spawn another somehow.
Our implementation being highly distributed with workgroups having full autonomy over their jobs - means every team needs to have access to Transporter. We have over 15 teams. Which is scary since that also takes resources from the CM - and also from a management and training perspective. We also haven't load tested the Transporter server interms of number of concurrent users that can be running Transporter on it at one time. Nor have any clear idea yet how we'll manage the mapping files. But we are also opening up Transporter to be installed by teams on their team server (only that they have to patch themselves) - I really wonder if we should just restrict Transporter access to just the servers our team manage and no one else can install it anywhere else.