You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the get_id_lists endpoint, would it be possible to get the blob contents of those lists into the Redis cache too, and have the HTTP server able to serve those blobs out of the cache?
At the moment the url on each entry in that cached response is something like https://idliststorage.blob.core.windows.net/idlists/.... , whereas ideally we'd have those saved and have the URLs all pointing to some endpoint like https://statsig-forward-proxy-domain:8000/idlists/... (where statsig-forward-proxy-domain would likely have to be something we pass in to tell the service what its public URL is)
Rationale
Improve availability and e2e latency by bringing the data blobs closer to origin.
The text was updated successfully, but these errors were encountered:
Request
For the get_id_lists endpoint, would it be possible to get the blob contents of those lists into the Redis cache too, and have the HTTP server able to serve those blobs out of the cache?
At the moment the url on each entry in that cached response is something like https://idliststorage.blob.core.windows.net/idlists/.... , whereas ideally we'd have those saved and have the URLs all pointing to some endpoint like https://statsig-forward-proxy-domain:8000/idlists/... (where statsig-forward-proxy-domain would likely have to be something we pass in to tell the service what its public URL is)
Rationale
Improve availability and e2e latency by bringing the data blobs closer to origin.
The text was updated successfully, but these errors were encountered: