IBM lab recommendation to include 15k-18k workitems in a plan in CLM4.0.6!
I am trying to include 15k-18k work items in a plan in CLM4.0.6.
Till RTC-2.0.0.1,we had IBM lab recommendation not to include work items more than 2048 beyond which shows decreased performance in the web client as well as eclipse client.
For CLM4.x (CLM4.0.6), I couldn't find any similar IBM lab recommendation which limits the users to add work items in a plan beyond which it will throw errors/warnings.
Do you have any recommendations or any documentation which explains the limits for work items in plans.
Please suggest.
Referred links:
https://jazz.net/forum/questions/106033/are-there-any-limits-on-number-of-work-items-a-plan-can-contain?redirect=%2Fforum%2Fquestions%2F106033%2Fare-there-any-limits-on-number-of-work-items-a-plan-can-contain
Till RTC-2.0.0.1,we had IBM lab recommendation not to include work items more than 2048 beyond which shows decreased performance in the web client as well as eclipse client.
For CLM4.x (CLM4.0.6), I couldn't find any similar IBM lab recommendation which limits the users to add work items in a plan beyond which it will throw errors/warnings.
Do you have any recommendations or any documentation which explains the limits for work items in plans.
Please suggest.
Referred links:
https://jazz.net/forum/questions/106033/are-there-any-limits-on-number-of-work-items-a-plan-can-contain?redirect=%2Fforum%2Fquestions%2F106033%2Fare-there-any-limits-on-number-of-work-items-a-plan-can-contain
Accepted answer
In RTC-1.x and RTC-2.x, there was a restriction that didn't allow you to view a plan if it had more than 2048 work items. In RTC-3.x, that restriction was removed, but as Sam points out once you have more than a few hundred work items in a plan, performance can degrade. I know some folks that successfully deal with 2000 work items in a plan, but others that (like Sam) start seeing degraded performance after a few hundred items. The common way to cut down the number of items in a plan is to request only plan items to be loaded, or if you need to look at execution items, focus the plan on a sub-iteration.
Comments
2 other answers
Hi Rohit,
Just came across :
https://jazz.net/wiki/bin/view/Deployment/CaseStudyRTCPlanLoadingPerformance
which has test results for plans containing different quantity of work items ranging from 333 to 9644.
Documented here is the Response time results comparing 3.0.1.3 and 4.0.3 using three browsers to access these plans with varied work item counts.
hope it helps.
Just came across :
https://jazz.net/wiki/bin/view/Deployment/CaseStudyRTCPlanLoadingPerformance
which has test results for plans containing different quantity of work items ranging from 333 to 9644.
Documented here is the Response time results comparing 3.0.1.3 and 4.0.3 using three browsers to access these plans with varied work item counts.
hope it helps.
2048?!..
best recommendation we got as no more than 200 workitems per plan. performance falls off greatly over this limit.
there were huge changes in the 4.x version compared to before.. and was significantly better, but performance still wasn't acceptable to my users. ( all of them using RTC via WAN connections from remote offices)
I don't think there are any physical limits, but they will be unmanageable once you get over 500 in my experience.
best recommendation we got as no more than 200 workitems per plan. performance falls off greatly over this limit.
there were huge changes in the 4.x version compared to before.. and was significantly better, but performance still wasn't acceptable to my users. ( all of them using RTC via WAN connections from remote offices)
I don't think there are any physical limits, but they will be unmanageable once you get over 500 in my experience.
Comments
