Closed GoogleCodeExporter closed 9 years ago
I'm having difficulty thinking of an actually efficient way to support that?
Original comment by wasserman.louis
on 15 Aug 2012 at 9:46
Perhaps this paper can supply some inspiration:
http://dhruvbird.com/lfu.pdf
Original comment by chir...@gmail.com
on 16 Aug 2012 at 12:58
...We may investigate this. That said, CacheBuilder does not specify its
eviction ordering, and leaves it open for implementations to decide: "As the
cache size grows close to the maximum, the cache evicts entries that are less
likely to be used again. For example, the cache may evict an entry because it
hasn't been used recently or very often."
Original comment by wasserman.louis
on 20 Aug 2012 at 8:42
Before we play with alternate eviction policies, we need to develop a means for
evaluating the impact of the different policies.
Original comment by kak@google.com
on 23 Oct 2012 at 4:16
(That note is just to explain why we won't be getting to this for a little
while.)
Original comment by kevinb@google.com
on 23 Oct 2012 at 4:19
Maybe the below would speed up the research.
https://tech.dropbox.com/2012/10/caching-in-theory-and-practice/
Original comment by anthony....@gmail.com
on 24 Oct 2012 at 7:01
Awesome, thank you.
Original comment by kevinb@google.com
on 24 Oct 2012 at 9:06
Original comment by kevinb@google.com
on 12 Mar 2013 at 6:43
This issue has been migrated to GitHub.
It can be found at https://github.com/google/guava/issues/<id>
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:13
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:18
Original comment by cgdecker@google.com
on 3 Nov 2014 at 9:08
Original issue reported on code.google.com by
chir...@gmail.com
on 15 Aug 2012 at 9:27