RPE 220.127.116.11 introduced the experimental Fast OAuth, a capability that was disabled by default and was limited to OAuth.
RPE 1.3 enables the fast authentication by default and extends it to Form and Basic authentication too. The tests we’ve made show considerable improvements in the time required to generate documents with fast authentication enabled.
What to expect
- The performance gain is directly proportional to the number of requests RPE has to make to get the data: the more requests, the bigger the performance gain is.
- The performance gain is inversely proportional to the size of the data returned by each request: the smaller the data, the larger the performance gain is as the % of the time spend to authenticate was also larger.
Here are some results obtained by our SVT and FVT teams:
Test 1: Form Authentication – a detailed test document ( +8000 pages) from CLM 4.0.6:
- Fast Auth disabled – 63,623 seconds. ( ˜17.6 hours)
- Fast Auth enabled – 5830 seconds. ( ~1.6 hours)
Test 2: OAuth – a detailed test document including test plan, test cases and TERs details from a the test plan containing 350 TERs from CLM 5.0.1. The template has many Dynamic Data Sources to get all the necessary details.
- Fast Auth disabled – 6873 seconds. ( ˜ 1hour 55 minutes)
- Fast Auth enabled – 628 seconds. ( ˜11 minutes)
Test 3: Basic Authentication – a document with data from 6,076 work items from Jazz.net:
- Fast Auth Disabled – 899 seconds
- Fast Auth enabled – 419 seconds
The results and performance gains depend on many factors in addition to the ones I’ve mentioned above such as data size, data structure and fragmentation, data location, template structure, hardware etc. You need to consider all these aspects when evaluating the performance gains you will observe with RPE 1.3 in your environment.