Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-41566

Cache the associated rubric call and avoid excessive http requests

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 19.0, 20.0 [Tentative]
    • Fix Version/s: 19.1, 20.0 [Tentative]
    • Component/s: Rubrics
    • Labels:
      None
    • 19 status:
      Verified
    • Test Plan:
      Hide

      Setup some Sakai properties. I used these:

      site.seed.create.sites=1
      site.seed.create.students=250
      site.seed.enrollments.per.site=250
      site.seed.create.gradebookitems=50

       

      (I've actually added these to the experimental server properties)

       

      Restart Sakai

      As 'admin', click on Job Scheduler

      Add a new job, call it whatever you want. Select 'Create sites, users and content for testing.'

      Click on the job and run it now.

      After a while you should see some auto created sites appear. Click on one of those and then on Gradebook. You should see a bunch of students, each graded against 50 items. It should take a few seconds to see the data. Now refresh the page, or click on 'Gradebook'. The data should load faster this time.

      Show
      Setup some Sakai properties. I used these: site.seed.create.sites=1 site.seed.create.students=250 site.seed.enrollments.per.site=250 site.seed.create.gradebookitems=50   (I've actually added these to the experimental server properties)   Restart Sakai As 'admin', click on Job Scheduler Add a new job, call it whatever you want. Select 'Create sites, users and content for testing.' Click on the job and run it now. After a while you should see some auto created sites appear. Click on one of those and then on Gradebook. You should see a bunch of students, each graded against 50 items. It should take a few seconds to see the data. Now refresh the page, or click on 'Gradebook'. The data should load faster this time.

      Description

      Cache the associated rubric call and avoid excessive http requests. Currently, every call to the rubrics service for the associated rubrics incurs an HTTP connection to the data rest endpoints. That operation, with 250 students and 25 items, takes around 2 seconds each time. Caching will improve that significantly, bringing it down to 1ms on subsequent requests.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  a.fish@lancaster.ac.uk Adrian Fish
                  Reporter:
                  a.fish@lancaster.ac.uk Adrian Fish
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code