Is there a limit to the number of Composer Workspaces that can be supported by a single jazz server?

There is no known theoretical limit for either, but there likely are practical limits. The RM performance team tested with particular profiles that are described in these articles in the jazz.net library, which were published earlier this year:

I am happy to see that there is no limit (at least theoretically) on the number of workspaces. That is good news!!!

How ever, I am still very concern............Assuming projects are equivalent to workspaces, it is nice to see an example with almost 50 works spaces and see the response time on that "enviroment".........

The DATA VOLUMEN section of the Performance Comparison article (very nice article) have some interesting data....I am assuming the "repository" means the total data on the Composer Jazz Server?

This is what I saw on that section.......:

The repository contained 200,000 artifacts and consisted of the following:

• Small Project Count: 40
• Medium Project Count: 9
• Total number of folders: 1,810
• Total number of requirement artifacts: 202,224
• Total number of collections: 282
• Total reviews: 325
• Total comments: 243,235
• Total public tags: 479
• Total private tags: 59
• Total term count: 13,304
• Total link count: 187,329

While this is a step forward .......My concern is, we are talking about creating several (and I mean in the order of thousands to start probably close to 3 thousand) workspaces and the expectation is there will be "hundreds" of link across several of those works spaces......same goes for folders, reviews, number of artfacts, links etc...and, we plan to have the whole CLM solution implemented.....not just Composer, so there will be links to "items" in other tools! ....To be fair, this may be perfectly okay using the JAZZ platform, and maybe I am worried for no reason....what we are trying to do sounds big and complex to me....but maybe this is what CLM is about and I just need to understand it better!

I see the recommended number of user is 400 for Composer 4.0.1.........That is also good news!

Any other word of advice? or document I can find good information on?

This does not directly address the scale question you mention above but there are plan items in the RM Backlog that will allow multiple RM servers, rather than the single RM server per JTS server that you have today. There are also other plan items investigating performance improvements.

• Remove functional load on JTS by moving RM store (44293, 60642)
• Support multiple RM servers sharing a single JTS (44261)
• Investigate how RM can support 1000 concurrent users (74775)
• RM Performance Goals for 2013 (60190)
  

This should not only improve performance but also improve the scale.

The idea is that each year to ensure continual performance improvement so that RRC is ahead of customer needs.

Mariana, it sounds like your deployment is going to be large enough that it would be a good investment to get some expertise from IBM or one of our business partners to help you plan your deployment. The way you organize your system (how many physical servers, how many software servers, etc. makes a large difference in the scaleability of the system.  Someone who has done this before can help you get it right the first time, share lessons based on what other large deployments have done, etc. If you need help figuring out who to ask for help, send me a note directly (dmoul at usdotibmdotcom)