-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
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
add more MemoryCache benchmarks #1606
add more MemoryCache benchmarks #1606
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
src/benchmarks/micro/libraries/Microsoft.Extensions.Caching.Memory/MemoryCacheTests.cs
Outdated
Show resolved
Hide resolved
cache.Remove(item.key); | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a SlidingExpiration
test as well? The above test is for absoluteExpirationRelativeToNow
AFAICT.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eerhardt we should, thanks for pointing this out! I could not find an extension method that would allow for setting SlidingExpiration
so I've changed all the benchmarks to use the using
pattern for adding the entries (used by the extension methods)
…mory/MemoryCacheTests.cs Co-authored-by: Eric Erhardt <[email protected]>
the CI failures are not related to this change, I am merging |
No description provided.