Limit componet per stream
2 answers
Hi Ramon,
from the sizing guide: https://jazz.net/library/article/551
Source Control: We recommend 50K files and folders in a single component and if you have more files to split them into multiple components. We encourage individual users to keep less than 300 change sets suspended. While there is no limitation, there is a tendency for a large suspended set can slow down operations involving the suspended set (suspend, resume, and discard) as well as add to some additional costs in refreshing or changing collaborations. 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.
from the sizing guide: https://jazz.net/library/article/551
Source Control: We recommend 50K files and folders in a single component and if you have more files to split them into multiple components. We encourage individual users to keep less than 300 change sets suspended. While there is no limitation, there is a tendency for a large suspended set can slow down operations involving the suspended set (suspend, resume, and discard) as well as add to some additional costs in refreshing or changing collaborations. 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.
Comments
Ralph,
I have a similar question.
I have slightly over 21,000 VM parts to transfer to RTC as individual components.
What would you suggest the best process is to transfer a large number of parts/components from VM to RTC?
I am using Eclipse RTC 3.0 which is needed to communicate to the VM system for compatibility.