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

Consuming data from Sumo - caching and transfer speeds #258

Open
sigurdp opened this issue Nov 13, 2023 · 0 comments
Open

Consuming data from Sumo - caching and transfer speeds #258

sigurdp opened this issue Nov 13, 2023 · 0 comments

Comments

@sigurdp
Copy link

sigurdp commented Nov 13, 2023

Some discussion points and topics that should be clarified regarding how Webviz can and should consume data from Sumo.

Reasons for wanting to cache data retrieved from SUMO could be:

  • Storing/caching computed/derived results
  • Need for transforming data to a more front-end friendly format
  • Better raw access speed, storing the data closer to the consuming service

What should be the rules/guidelines for caching in clients wrt. SUMO data?

  • Is caching allowed?
  • Where (backend, user's browser)?
  • For how long can data be cached?
  • Is it permissible/technically possible to cache data on a higher level than per user:
    • Access groups etc?
    • Based on roles?
  • Are permissions configured on a per blob-granularity or can we make assumptions based on the granted access to metadata?

Expectations wrt data transfer speed between SUMO and backend services/clients:

  • What is the expected raw data transfer speed between SUMO and clients (e.g. Webviz)?
  • Experiments so far indicate mediocre transfer speeds, but this may not be correct
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

1 participant