It's all about the answers!

Ask a question

recommended number of components in a stream / RTC / ProjectArea

Karthik Krishnan (8825118163) | asked Jan 14 '15, 11:10 a.m.
Are there any recommended limit for number of components in RTC / single Project Area?

Accepted answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Jan 15 '15, 1:22 a.m.
edited Jan 15 '15, 1:23 a.m.
There is no limit from a database perspective.
Note that a component does not really belong to a Project Area ... it just has an owner field (which determines read-access to that component) which can be set to a Project Area.  
The practical limits are usability limits in the UI.   In particular, if you have hundreds of components in a project area, stream, or workspace, scrolling through the GUI lists of components to find the one you want will be clumsy.
So ideally, 50 or fewer components in a given stream/workspace that is frequently accessed is ideal.
A few hundred in a stream/workspace that isn't accessed that frequently (in the GUI) is ok.
I personally would never put more than a few hundred in a stream/workspace.
Note that there is a high priority plan item for the SCM team to allow the definition of "hierarchical components", which should remove this constraint on the number of workspaces in a given stream/workspace.

Karthik Krishnan selected this answer as the correct answer

Karthik Krishnan commented Jan 15 '15, 5:19 a.m.

Thank you Geoff

Yes you are correct with the GUI aesthetics. I wanted to know from the DB / performance perspective.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.