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

Add caching to improve the performance of data retrieval operations #252

Closed
edwinmp opened this issue Jul 27, 2020 · 3 comments · Fixed by #503 or #533
Closed

Add caching to improve the performance of data retrieval operations #252

edwinmp opened this issue Jul 27, 2020 · 3 comments · Fixed by #503 or #533
Assignees
Labels
enhancement New feature or request Frontend pinned

Comments

@edwinmp
Copy link
Collaborator

edwinmp commented Jul 27, 2020

Benchmark and settle on the ideal service for our needs
https://aws.amazon.com/redis/
https://aws.amazon.com/elasticache/redis-vs-memcached/

https://www.digitalocean.com/products/managed-databases-redis/

@edwinmp edwinmp added the enhancement New feature or request label Jul 27, 2020
@edwinmp edwinmp added this to Backlog in Phase Two Features via automation Jul 27, 2020
@edwinmp edwinmp moved this from Backlog to To Do in Phase Two Features Jul 27, 2020
@edwinmp
Copy link
Collaborator Author

edwinmp commented Jul 28, 2020

Front-end caching could do as well ... should guarantee that a query is only slow to run the first time & for when the cache has been cleared. Adding a graphql layer to the API could help with this. Otherwise, we could use localforage

@edwinmp edwinmp moved this from To Do to Backlog in Phase Two Features Aug 7, 2020
@stale
Copy link

stale bot commented Feb 17, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Feb 17, 2021
@stale stale bot closed this as completed Feb 24, 2021
Phase Two Features automation moved this from Backlog to Done Feb 24, 2021
@edwinmp edwinmp added pinned and removed wontfix This will not be worked on labels Feb 24, 2021
@edwinmp edwinmp reopened this Feb 24, 2021
Phase Two Features automation moved this from Done to To Do Feb 24, 2021
@edwinmp edwinmp moved this from To Do to Backlog in Phase Two Features Feb 24, 2021
@edwinmp edwinmp moved this from Backlog to To Do in Phase Two Features Mar 17, 2021
@edwinmp edwinmp added Frontend and removed Backend labels Mar 17, 2021
@davidebukali davidebukali moved this from To Do to In Progress in Phase Two Features Mar 30, 2021
@davidebukali davidebukali self-assigned this Mar 30, 2021
@davidebukali davidebukali moved this from In Progress to Code Review in Phase Two Features Apr 22, 2021
@edwinmp edwinmp linked a pull request Apr 22, 2021 that will close this issue
@edwinmp edwinmp moved this from Code Review to Functional Review in Phase Two Features Apr 26, 2021
@edwinmp
Copy link
Collaborator Author

edwinmp commented Apr 26, 2021

Caching has only been added to the query data page, so this is still incomplete.

What's left:

  • My Datasets
  • Published Datasets

@edwinmp edwinmp moved this from Functional Review to Deploy to Live in Phase Two Features Apr 27, 2021
@edwinmp edwinmp moved this from Deploy to Live to In Progress in Phase Two Features May 3, 2021
@edwinmp edwinmp moved this from In Progress to Functional Review in Phase Two Features May 11, 2021
@edwinmp edwinmp moved this from Functional Review to Deploy to Live in Phase Two Features May 17, 2021
@edwinmp edwinmp linked a pull request May 27, 2021 that will close this issue
@edwinmp edwinmp closed this as completed May 27, 2021
Phase Two Features automation moved this from Deploy to Live to Done May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Frontend pinned
Projects
Development

Successfully merging a pull request may close this issue.

3 participants