The multi-generational LRU
The multi-generational LRU
Posted Apr 8, 2021 14:01 UTC (Thu) by smurf (subscriber, #17840)In reply to: The multi-generational LRU by yuzhao@google.com
Parent article: The multi-generational LRU
Did you identify any workload that fares worse under your algorithm? One may assume that Google has quite a few wildly different workloads to experiment with …
Posted Apr 13, 2021 9:09 UTC (Tue)
by yuzhao@google.com (guest, #132005)
[Link]
Your assumption is correct. But our "wildly different workloads" are only a fraction of all real-world workloads. AFAIK, we don't use Postgresql, and we do plan to reach out to the Postgresql community and see if they could help us with benchmarking.
And we don't use io_uring (yet). Jens Axboe, the io_uring maintainer helped us identify a regression in buffered I/O and verify the fix. Now there is an improvement compared with the mainline: https://lore.kernel.org/linux-mm/20210413065633.2782273-1...
By design, the multigenerational LRU shouldn't make any workload worse -- why should it make worse decisions after it gathered more information? But that's just the theory :)
The bottomline is we'll do our best to fix any regressions the community reports to us. Again, the email address is page-reclaim@google.com.
The multi-generational LRU