Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Expiry after Access / Time to Idle #39
Expiry after an entry is accessed. This is (should be) primarily intended for freeing resources if not used, while expiry after modification is an optimization versus business decision (how old is okay?).
For efficiency reasons I intend to do it not 100% on time but with a defined maximum lag.
Time an entry expires after an access. By default there is lag of 10%, which means the actual expiry might be later then specified. Example: Configured value is 1h, the item may stay in the cache and keep visible for a maximum of 1 hour and 6 minutes after an access.
Configure a different lag time. The minimum lag time is 1 minute.
changed the title from
Expiry after Access
Expiry after Access / Time to Ilde
Mar 29, 2016
@ricardojlrufino Thanks for reaching out! Its good timing, since I have now stabilized the next version (1.2) and need to do some planing what important stuff to put the focus on next.
Two reasons it's not there yet: We rarely need it, there needs to be always a compromise on the performance we have achieved to provide/enable this feature.
To drive it in the right direction, I'd love to hear from people who actually need it. Can you share something about the scenario you want to use it for?
@cruftex My application is from IoT and I cache the Devices in use and, after a while, I need to remove it from memory.