Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Selector Performance Information

As part of the web-based Higgins deployment, performance tests were run for single user (with 2 information cards) to benchmark the performance parameters of the card selector. From these tests is was found that as part of the user profile operation there was a specific Jena based call, specifically: Jena based IdasBasedUserProfileService on RPPS component.

After initial tests found this user profile call to be the biggest performance impact, some Jena query optimizations were completed and a new test round was conducted. The following graphs highlight the different before and after Jena optimization test results.

Note for the bar graph on the right the times are plotted on log scale.

Selector PerfImprovment1 Jan08.PNG Selector perfImprovment2 Jan08.PNG

The test numbers referenced in the above graphics are the response time for the specific calls defined as follows:

  1. The following 4 calls encompass the time it takes for the card selector window to pop up with the group of cards that match the RP claim requests:
    • Test 110 - /RelyingPartyDemoApp/protected/index.jsp
    • Test 120 - /rpps-axis/services/RPPSService?WSDL
    • Test 130 - /[RPPS]getTokenByUrl
    • Test 140 - /[RPPS]getUI
  2. The following 2 calls account for the time it takes for the login to the RP site once the user selects their login card and clicks "Next" on the selector
    • Test 150 - /[RPPS]getTokenObject
    • Test 160 - /RelyingPartyDemoApp/Login

Even after the dramatic performance improvement, the largest performance impact is with the RPPS getTokenObject call. This is due to the key generation call. Specifically the bulk of the processing time is spent in There is a Higgins Bugzilla ticket logged against this issue 215874. At this time there does not appear to be much that can be done to improve this key generation process time - save a mid-term solution (per Mike McIntosh) that would involve extending the card store to cache the generated key pairs for each RP so this process does not happen each time a card is used(it would only happen the first time for each RP).

Back to the top