Many storr functions already have a use_cache argument to avoid interactions with the file system. What about a similar cache that keeps track of the names of the key and/or data files in the cache, with the ability to pre-populate it when the storr initializes? I am struggling with slowness from repeated calls to file.exists() via set_value() benchmarks here.
Many
storrfunctions already have ause_cacheargument to avoid interactions with the file system. What about a similar cache that keeps track of the names of the key and/or data files in the cache, with the ability to pre-populate it when thestorrinitializes? I am struggling with slowness from repeated calls tofile.exists()viaset_value()benchmarks here.