Rational EM products (RTC EE, RDz, RD&T, RAA, …): recommendations and “educated guesses” for limitations

In the past couple of years, I’ve helped customers in their adoption and deployments of CLM, RTC, RQM and RRC-DNG. Based on their recurrent questions for correct sizing and scalability handling, I shared some limits / educated guesses for limitations in the blog post “CLM,RTC,RQM,RRC: recommendations and “educated guesses” for limitations“.

RationalEM-TableofLimitsNow that my focus has moved to Rational Team Concert Enterprise Extensions (RTC EE) and the Rational solution for Enterprise Modernization, I want to share similar content for RTC EE, RDz, RAA, … Following the same approach. [Tip for you] if you’re already familiar with my previous post, you may skip straight to the tables below and ignore the two following sections which detail some terminology and purpose aspects.

In the Tables below, there are columns for Limits and Alert zone. Let’s clarify how we define them:

  • Quantified data: the (maximum) number of….
  • Limit: a hard limit of the product. Meaning that you cannot go beyond this value.
  • Alert zone: based on experiences with customers, internal tests and development teams, it’s around these values that we start seeing performance issues. If you’re approaching these values, we’d suggest you monitor your system closely to detect any performance degradation before it becomes critical. WARNING: while provided figures are educated guesses and practical rules of thumbs, you could still find that your environment functions perfectly beyond these limits  (e.g. if your environment is particularly fine-tuned). In a similar way,  some intense usage could show that these recommended values are too optimistic…

As a consequence, it’s important to understand this post is NOT an attempt for replacing existing resources (see the References section) that provide extensive views on CLM performance and tuning topics. We encourage administrators and project managers to read them as they both include finer-grain information and insist on the key aspect of not loosing the “bigger picture”.

What’s the use of the following tables then ?

Answer: they’re here to HELP YOU quickly figure out if you’ve reached some known limitation or if you’re getting close to a threshold  (again: on the basis of a typical/average environment) requiring due monitoring of your environment.  To this regard, these tables are COMPLEMENTARY with existing resources and concentrate information ALREADY available ((but yet disseminated) on multiple medias/sites/forum posts/etc.

Now, let’s go straight to the tables…

RTC EE
Quantified data Limit Educated guess / Alert zone Reference(s)
Files
   Files in a component (<v4.0) 2000 Dev team inputs
   Files in a component (>=v4.0)  –  2000 [Share 2013] (s. 8)
Build
   builds in parallel (*) number of build engines supporting the build definition
   team builds in parallel (<4.0.3)  –  1 (**) Jazz.net forum, EEBAW workshop labs (p. 63)
   team builds in parallel (>=4.0.3)  1 Jazz.net WI (***)
   team builds in parallel (>=4.0.6)  –  1 Jazz.net WI (****)
 
(*): this includes personal and team builds.
(**): multiple concurrent team builds of your dependency build may result in unnecessary rebuilds of the same program. You should prevent this by only configuring one supporting team build engine. Additional engines may be added for personal builds only. Check referenced EEBAW workshop labs for more details.
(***): from this 4.0.3 version level, when running multiple team builds in parallel, all but the 1st treated of the concurrent build requests will fail and error log will contain the following message: “Found a build “20140319-xxxxxxxxxx” “currently running.  Running concurrent builds is disallowed.
(****): constraint possibly relaxed by both setting the mentioned property and by making sure you use non overlapping subset. Typical use case is (only) for building different programs (a.k.a non-incremental team builds).

Ξ

RDz
Quantified data Limit Educated guess / Alert zone Reference(s)
 – [RDz v9 InfoCenter] Tuning considerations

Ξ

RD&T
Quantified data Limit Educated guess / Alert zone Reference(s)
developers supported  –
  • 3-5 per RD&T server (Desktop machine)
  • 15-25 per RD&T server (Server class machine)
[Share 2012] (s. 32)
defined System z CPs (*)
  • 1 (1090-L01 model)
  • 2 (1090-L02 model)
  • 3 (1090-L03 model)
[Redbook] (p.12)
defined System z CPs (*) associated to a single zPDT instance
  • one less than the # of processor cores on the base Linux system (**)
 3-4 (***) [Redbook] (p.12)
zPDT instances  1 (per System z CP) [Redbook] (p.12)
emulated I/O devices  1024 [Redbook] (p.21)
 
(*): or mixture of CPs, zIIPs, zAAPs, and IFLs.
(**): an exception exists for a single core, which may be used with reduced zPDT (check p.3 of the referred Redbook).
(***): as per the I/O capability of the underlying PC and various “SMP effects”. Check p.12 for more details. Note: for configurations including multiple z1090 tokens, check p. 13 of referenced Redbook.

Reference for functional restrictions and scope exclusions inherent to a RD&T usage (in comparison to a real mainframe):

  • while these topics are not targeted in this document, for you awareness, you could find a consolidated list in the following resource (slide 25).

Ξ

RAA
Quantified data Limit Educated guess /Alert zone Reference(s)
number of levels for impact analysis  100 [WSAA InfoCenter] (p.47)
max. size of a scanned file  5 Mo (*) [devWorks forum]
 
(*): default value extendable through a property. Check referred forum answer for details.

References:

  1. [Deployment wiki] Performance datasheets and sizing guidelines
  2. Rational Team Concert 4.x sizing report for z/OS
  3. Rational solution for CLM 4.0 performance tuning guide for z/OS  (Oct 2012)
  4. General Link: Rational Developer for System z (RDz)
  5. General Link: Rational Development and Test Environment for System z (RD&Tz)
  6. General Link: Rational Asset Analyzer (RAA)

Acknowledgment/Credit: thanks to the authors of the cited documents above and more generally to the Jazz community who collaboratively provides accurate information through library articles, forums questions & answer, etc..

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: