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.

Sign up for GitHub

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

Jump to bottom

ageLimit is not an ageLimit #76

Open

albsala opened this issue Feb 3, 2015 · 0 comments

albsala commented Feb 3, 2015

If I'm not mistaken, when I set an ageLimit, TMCache trims cache by age and repeat the operation every "ageLimit" using dispatch_after.

If I set an ageLimit of 10 sec on t=0, insert an object on t=5, that object keeps in cache for 15 sec.

I think this is not the expected behavior.

Problem becomes worse when ageLimit becomes larger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment