Closed midsterx closed 1 year ago
Hi @midsterx, Belady is only supported on oracleGeneral traces which you can find some from https://ftp.pdl.cmu.edu/pub/datasets/twemcacheWorkload/cacheDatasets/
The oracleGeneral traces have future request information that is used by Belady, csv traces do not have this. I hope this helps.
Thank you for clarifying this @1a1a11a! I am guessing that no other eviction algorithms use future request information. Is that right?
yes, other algorithms do not use future information (unless the name has Belady or suggests so)
BTW, when you do not use "--ignore-obj-size 1" cmd option, you need to use BeladySize
algorithm instead of "Belady"
Let me know if you encounter other problems
If you would like to contribute and clarify this in README, we welcome all PRs :)
Hey @1a1a11a, I have created the following PR for the clarifications: https://github.com/1a1a11a/libCacheSim/pull/30
I have also created the following PR to address the default value while parsing --ignore-obj-size
: https://github.com/1a1a11a/libCacheSim/pull/31
The previous value of True does not allow users to consider the object size.
Thank you!
Hi,
I am currently using this library to understand the eviction algorithms that I should be exploring. However, both the MRCs over size and MRCs over time seem to indicate that Belady is the worst performer. Am I missing something here? MRC over sizes:
MRC over time:
The commands that I have used to obtain the plots are as follows (similar to those found in https://github.com/1a1a11a/libCacheSim/tree/develop/scripts#plot-miss-ratio-curves, with
belady
added as an additional algorithm):