How many components we can create in a Stream?
3 answers
According to this Jazz article:
We have tested the user experience of working with a large number of components in workspaces and streams. There are no known issues with having hundreds of components in a stream or workspace, and we have tested the user experience with 500 components in collaboration.
and this Wiki article:
|
|
|
Recommendation
less than 500 |
Before hierarchical components (which is when the referenced article was written), there were UI usability limits for the number of components in a single stream or workspace, which resulted in the recommendation of no more than 500 components in a single stream or workspace (this was not a hard limit ... it was a usability limit). With the addition of hierarchical components, this recommendation has been increased to no more than 2500 components in a single stream or workspace (but only if you use hierarchical components to control the number of components at a given level of the hierarchy, preferably no more than 50 or so child components for a given component).
Before hierarchical components (which is when the referenced article was written), there were UI usability limits for the number of components in a single stream or workspace, which resulted in the recommendation of no more than 500 components in a single stream or workspace (this was not a hard limit ... it was a usability limit). With the addition of hierarchical components, this recommendation has been increased to no more than 2500 components in a single stream or workspace (but only if you use hierarchical components to control the number of components at a given level of the hierarchy, preferably no more than 50 or so child components for a given component).