We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In MemoryCache by Microsoft we can do things like
public class MyMemoryCache { public MemoryCache Cache { get; } = new MemoryCache( new MemoryCacheOptions { SizeLimit = 1024 }); }
or
Action<MemoryCacheOptions> action = options => { options.SizeLimit = 1024; }; services.AddMemoryCache(action);
Is there a way to limit the total size of the LazyCache?
If not, this should be your next feature to implement in my opinion.
This is why it is important
The text was updated successfully, but these errors were encountered:
I have figured out a way to do it, not entirely sure yet that LazyCache will use this configuration, maybe @alastairtree can confirm this
/// <summary> /// Our caching implementation /// </summary> public class OurLazyCaching : CachingService { /// <summary> /// Our custom caching options, configure in appsettings? /// </summary> private static readonly IOptions<MemoryCacheOptions> _options = new MemoryCacheOptions { SizeLimit = 1024 // unitless size }; /// <summary> /// Constructor that applies our custom caching options /// </summary> public OurLazyCaching() : base(new Lazy<ICacheProvider>(() => new MemoryCacheProvider(new MemoryCache(_options)) ) ) { } }
And than use this in the denpendency injection services.AddSingleton<IAppCache, OurLazyCaching>();
services.AddSingleton<IAppCache, OurLazyCaching>();
Sorry, something went wrong.
No branches or pull requests
In MemoryCache by Microsoft we can do things like
or
Is there a way to limit the total size of the LazyCache?
If not, this should be your next feature to implement in my opinion.
This is why it is important
The text was updated successfully, but these errors were encountered: