Skip to content

feat: enabled local cache to reduce the usage of the shared cache

Diego Molteni requested to merge slb/dm3/local-cache-5 into master

This change will reduce the usage of the shared cache in SDSM. Meta information and results will be locally cached to improve overall performances. Only the distributed locker will continue to use the shared cache.

These is the list of entities, previously saved in the shared cache, that we will be moved in the local/in-pod managed cache.

  1. Tenant Metadata
  • accessed at each call to SDMS
  • TTL 1h, no changes to service behavior
  1. Exchanged Token
  • accessed only in case token is required to be exchanged with a different audience
  • TTL 5m, no changes to service behavior
  1. CCM User Association
  • accessed every time dataset metadata is retrieved
  • TTL 1h, no changes to service behavior
  1. Legal Tag Validation
  • accessed at each call to SDMS
  • TTL 1h, no changes to service behavior
  1. Entitlement Authorization Validation
  • accessed at each call to SDMS
  • TTL 1m, no changes to service behavior
  1. Azure Storage access keys and configurations
  • accessed every time a storage operation is required (create subproject / get storage access token)
  • TTL 1h, no changes to service behavior
  1. Azure Cosmos access keys and configurations
  • accessed every time a dataset is created, retrieved, or listed
  • TTL 1h, no changes to service behavior
  1. Subproject Metadata
  • accessed at each call to SDMS
  • TTL 10s, introduce eventual consistency on patch operation
  1. AWS tenant ID from partition ID
  • accessed at each call to SDMS
  • TTL 1h, no changes to service behavior

Merge request reports