I'm sure it's been done before, but right now I feel smart about the recognition. I want to make postgres' buffer cache take into account whether previous accesses where synchronous or asynchronous:
But I hope it'd be more generic (i.e. also keep randomly accessed table pages around) and resilient (doesn't trigger due to vacuum scanning the index).
-
-
I agree with this. I just really like the framing from the LRU-K paper, which is very simple but totally convincing -- see example 1.1: https://www.cs.cmu.edu/~christos/courses/721-resources/p297-o_neil.pdf …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.