Cache API responses to speed up dashboard navigation

Open
#38 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend, web-dev

Research direction

No files or tests are named. Start by locating the dashboard data-loading and fetch calls, then trace how navigation and test switching request Treeherder data. Done means JSON responses use IndexedDB caching with a 15–30 minute TTL, fetch fallback, and a way to force fresh data through a “Refresh Data” button.

Written by the indexing model from the issue text.

Description

Every page load re-fetches all data from Treeherder. Navigating between dashboards or switching back to a previous test means waiting for all of it again.

We could cache JSON responses in IndexedDB (sessionStorage is too small for the payloads). Something like a cachedFetch() wrapper with a 15-30min TTL that falls back to fetch() if it fails. We can also add a "Refresh Data" button so you can force fresh data when needed.

Dominant language
JavaScript
Stars
7
Forks
11
Avg merge
4m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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.

More from mozilla/performance

All issues in mozilla/performance

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.