lookit / lookit/lookit-api

Review & optimize API calls made during study start

Open
#476 0 comments 0 reactions 1 assignee View on GitHub

@kimberscott is already working on this.

Since Apr 3, 2020.

Performance Tuning Scoping
Dominant language
Python
Stars
12
Forks
21
Avg merge
5d 19h
Merged PRs (30d)
5

Description

Currently (a) the frameplayer makes a bunch of perhaps unnecessary API calls when starting a study session and (b) those calls are inefficient, leading to long load times esp. if there are previous sessions.

How to replicate:

1. Create a study on local lookit-api instance; make active & public (need to set 'active' state through admin interface to avoid requiring the study be properly "built" , or set "built" flag via admin interface)
2. Participate in study by going to localhost:4200/studies// - make about 10-20 responses just by refreshing page. See https://lookit.readthedocs.io/en/develop/frame-dev-setup.html for setup instructions to get ember-lookit-frameplayer & lookit-api to talk with each other.
3. Observe loading of page (e.g. using Django debug toolbar) & see if API calls & their load times make sense - this has been taking ~10-20s for Kim

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.