Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Backlog
    • Fix Version/s: Not version specific
    • Component/s: Quality Assurance
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13528Develop way to automate performance grid updates
      KULRICE-13643Finish performance grid for Jerry
      KULRICE-14094Develop test scenarios for KC performance
      KULRICE-11147Provide grid layout beans with Bootstrap table styles
      KULRICE-13457Create grid of Rice and correlating KRAD screens, with Responsiveness requirements
      KULRICE-14075Performance Profiling of KC
      KULRICE-7186Change grid layout to generate td instead of th when only one cell is being rendered (and not first line)
      KULRICE-11170Create performance test plan
      KULRICE-13814Run the smoke tests on the grid
      KULRICE-13559Create Performance View load tests
    • Rice Team:
      QA
    • Application Requirement:
      KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Similar to KULRICE-13643, create a performance grid parsing KC/Rice performance data.

        Activity

        Hide
        Adam Campbell (Inactive) added a comment -

        Begin manually recording response times and document on grid.

        Show
        Adam Campbell (Inactive) added a comment - Begin manually recording response times and document on grid.
        Show
        Adam Campbell (Inactive) added a comment - https://docs.google.com/a/kuali.org/spreadsheets/d/1V0QWb_xja7DFuTwnZchtywDXK1KMrigyK40NgwffEeY/edit#gid=1138680563
        Hide
        Adam Campbell (Inactive) added a comment -

        Notes from Jerry:

        Just wanted to get a couple things organized in terms of the performance tuning. We have three top areas to target initially:

        Questionnaire
        Data Validation Toggle
        Key Personnel Wizard
        Initial Load

        So that we can gauge our progress, I was hoping Adam and Dan can start monitoring these response times in test. I know Dan is working on AFTs, but in the meantime Adam can manually record the responses times each day and produce a grid for us. If everyone is good with that (including Adam), can you provide information to Adam on where to go?

        I have started profiling and capturing notes here:

        https://docs.google.com/a/kuali.org/document/d/1ovmISBByNylR1NGSQ9eE8-5Dk0wDctgyAkJ8uT5clGQ/edit#heading=h.uqaax4xu04ho

        KIM is the big killer. I have only fully profiled the first target, but captured others as well and the KIM calls are always at least 50% of the response time (sometimes more than 90%). The good news is I think there is an easy win here in that we should not need to make these checks on every call (changing pages, getting dialogs, etc.). If we can get this down to just one set of calls, it will really cut down time on subsequent calls. And I think we can tune the one set to not be as bad. Data access tuning will be a bit more hairy, but there are definitely clear areas to look at.

        Show
        Adam Campbell (Inactive) added a comment - Notes from Jerry: Just wanted to get a couple things organized in terms of the performance tuning. We have three top areas to target initially: Questionnaire Data Validation Toggle Key Personnel Wizard Initial Load So that we can gauge our progress, I was hoping Adam and Dan can start monitoring these response times in test. I know Dan is working on AFTs, but in the meantime Adam can manually record the responses times each day and produce a grid for us. If everyone is good with that (including Adam), can you provide information to Adam on where to go? I have started profiling and capturing notes here: https://docs.google.com/a/kuali.org/document/d/1ovmISBByNylR1NGSQ9eE8-5Dk0wDctgyAkJ8uT5clGQ/edit#heading=h.uqaax4xu04ho KIM is the big killer. I have only fully profiled the first target, but captured others as well and the KIM calls are always at least 50% of the response time (sometimes more than 90%). The good news is I think there is an easy win here in that we should not need to make these checks on every call (changing pages, getting dialogs, etc.). If we can get this down to just one set of calls, it will really cut down time on subsequent calls. And I think we can tune the one set to not be as bad. Data access tuning will be a bit more hairy, but there are definitely clear areas to look at.
        Show
        Adam Campbell (Inactive) added a comment - https://docs.google.com/a/kuali.org/spreadsheets/d/1V0QWb_xja7DFuTwnZchtywDXK1KMrigyK40NgwffEeY/edit#gid=1138680563
        Hide
        Adam Campbell (Inactive) added a comment -

        Jerry:
        [12/10/14, 9:21:59 AM] Jerry Neal: http://test.kc.kuali.org/kc-trunk/kc-krad/landingPage?methodToCall=start
        [12/10/14, 9:22:17 AM] Jerry Neal: You should see menu bar with 'Reseacher'. click that and the first link is 'create proposal'

        Just create new proposal. Fill out anything for the first page, only the last field has to be valid. Enter 10 and you will get a suggestion. Then click the continue button. This is the first request we want to capture. Do this a few times and record the average time. Now once you are here, click on the questionarie page in the left menu. this is a second one we want to capture time. Now click on the Data Validation link in the header. Once the dialog comes up click the turn validation on button. This is a third request to capture. For the last one go to the Personnel page in the left menu. Click the button 'Add Personnel'. This will start the wizard. Capture each request of the wizard (4 total). for the search, you can leave the criteria blank

        Show
        Adam Campbell (Inactive) added a comment - Jerry: [12/10/14, 9:21:59 AM] Jerry Neal: http://test.kc.kuali.org/kc-trunk/kc-krad/landingPage?methodToCall=start [12/10/14, 9:22:17 AM] Jerry Neal: You should see menu bar with 'Reseacher'. click that and the first link is 'create proposal' Just create new proposal. Fill out anything for the first page, only the last field has to be valid. Enter 10 and you will get a suggestion. Then click the continue button. This is the first request we want to capture. Do this a few times and record the average time. Now once you are here, click on the questionarie page in the left menu. this is a second one we want to capture time. Now click on the Data Validation link in the header. Once the dialog comes up click the turn validation on button. This is a third request to capture. For the last one go to the Personnel page in the left menu. Click the button 'Add Personnel'. This will start the wizard. Capture each request of the wizard (4 total). for the search, you can leave the criteria blank

          People

          • Assignee:
            Adam Campbell (Inactive)
            Reporter:
            Adam Campbell (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel