How to break down a very large component for RTC builds
We currently have a component on our mainframe system that has 160,000 files. We are looking to find what 'best practices' are being used by others for building large components in RTC.
What is a good size limit for components - # of files, etc? Does anyone have information on performance considerations for large components? |
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Mar 01 '11, 2:26 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Karen,
There is a statement in the sizing guide that says that we tested up to 500 components. There is also a statement that we recommend up to 50k files and folders in a component. With respect to best practices, our guidance has typically been to break up components following architectural pattern. Split up into components avoiding circular dependencies and components should also contain something that logically belongs together. So layers, fundamental reused parts of the application and aspects such as UI etc. are typical pattern. Thanks, Ralph We currently have a component on our mainframe system that has 160,000 files. We are looking to find what 'best practices' are being used by others for building large components in RTC. Comments We are also seeing a performance issue in one of our component. Where can we find these documentations listing the max limits for component file count.
Vince Thyng
commented Sep 06 '13, 2:34 p.m.
Lakshmana, you can find these limits in the sizing guide:
|
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.