Consuming data from Sumo - caching and transfer speeds - Githubissues

equinor / fmu-sumo

Interaction with Sumo in the FMU context

https://fmu-sumo.readthedocs.io/en/latest/

Apache License 2.0

0 stars 5 forks source link

Consuming data from Sumo - caching and transfer speeds #258

Open sigurdp opened 7 months ago

sigurdp commented 7 months ago

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