News for hackers. Stuff that matters.

A comment on DragonFlydb: Cache Design. Parent comment

Re:DragonFlydb: Cache Design by heisjustsosmart on Tuesday August 16, 2022 @02:12PM (#32486580)
Think you mean round robin, yes, that's an issue but that's equal probability, not high probability (his phrase). I don't know a scheduler that will handle that as well as handling LRU replacement well and if you have any cites I would appreciate them.

Also remember that many DBs are multi-user so any access patterns from each connection will get thrown in the same bucket.

[ Parent | on HN ]
Re:DragonFlydb: Cache Design by NovaX on Tuesday August 16, 2022 @02:31PM (#32486822)
It is handled by W-TinyLFU where I use this scenario as a stress test [1]. While LIRS / LIRS2 did not pass this one scenario, the quality of the work behind that policy leads me to believe it could be improved to handle that case.

[1] https://github.com/ben-manes/caffeine/wiki/Efficiency#adapti...

[ Parent | on HN ]