Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Report Loading Performance on Public Facing site #351

Open
KipSigei opened this issue Jan 17, 2022 · 0 comments
Open

Improve Report Loading Performance on Public Facing site #351

KipSigei opened this issue Jan 17, 2022 · 0 comments
Assignees

Comments

@KipSigei
Copy link
Contributor

KipSigei commented Jan 17, 2022

Upon initial site load, we normally aggregate data from the first admin level (Region) to the last level (Station). This initial process is quite heavy for the front end code since we need to iterate through several reports which include:

  • centers and stations report
  • candidates list
  • forms list
  • results report
  • offices list
  • regions list

The largest report so far is the forms list report followed by the results report, which both have a combination of parliamentary and presidential data. As a temporary solution, we have added logic that aggregates data from the highest to the lowest admin level and set it to local storage, meaning the only time the user will experience latency is on initial load, and when drilling down to the other levels there's no significant latency experienced. We need to find a way to improve the initial load performance, maybe by splitting the files based on the race type, or have this data pre-aggregated from the tally system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants