Requirements Composer performance and scalability
As the use of RRC grows within an organization, I would expect that there is some point at which it makes sense to use WAS instead of Tomcat because of performance and scalability. Have any guidelines been developed giving some recommendations on number of projects, artifacts, or users that might help make this determination?
Should an organization with 30 in-flight projects use WAS? 50? 100?
Should an organization with 30 in-flight projects use WAS? 50? 100?
One answer
As the use of RRC grows within an organization, I would expect that there is some point at which it makes sense to use WAS instead of Tomcat because of performance and scalability. Have any guidelines been developed giving some recommendations on number of projects, artifacts, or users that might help make this determination?
Should an organization with 30 in-flight projects use WAS? 50? 100?
For some performance testing please see this whitepaper:
http://www.ibm.com/developerworks/rational/library/10/rrcperformanceandscalablitytestresults/index.html
The issues tends to be the number of users, and the amount of memory on the application server, and total number of artifacts rather than the number of projects
Note:
We used the default WebSphere Application Server configuration. No additional performance tuning was performed on WebSphere Application Server when running our tests.
The difference in average response times for each user grouping is never greater than 55 ms. For smaller-scaled shops with fewer than 300 users, choose the application server that is available and suits your particular needs."