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

Investigate where the form_builder_service can be improved with caching #521

Open
4 tasks
dleard opened this issue Jan 27, 2025 · 1 comment
Open
4 tasks
Labels
API Tickets related to the API Exploration Tech Debt

Comments

@dleard
Copy link

dleard commented Jan 27, 2025

The form_builder_service could probably be optimized by caching some of the queries. Several of the queries are returning data that won't change in a short period of time (ie: ConfigurationElements). When passed several source-types worth of data, the build-form-schema endpoint can start to become very slow.

The delay in server response & quickly checking/unchecking source types can cause confusing results. Could also consider disabling the checkboxes until the response has come bac

Developer Checklist:

  • investigate where caching might help in the form-builder-service
  • implement the optmizations
  • check django-silk when hitting that endpoint with several source-types (suggest OG Extraction, it has > 20 potential source types)
  • consider disabling checkboxes on check/uncheck until server has responded
@dleard dleard added Exploration Tech Debt API Tickets related to the API labels Jan 27, 2025
@dleard
Copy link
Author

dleard commented Jan 27, 2025

@Sepehr-Sobhani @pbastia I've noticed that the build-form-schema endpoint gets quite slow when selecting several source types at a time (up until now, we've only ever had 3 source types maximum, but OG Extraction has >20 potential source types) so I've made this card to investigate how we can optimize that service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Tickets related to the API Exploration Tech Debt
Projects
None yet
Development

No branches or pull requests

1 participant