search

sunnyszy / lrb

A C++11 simulator for a variety of CDN caching policies.
BSD 2-Clause "Simplified" License
78 stars 28 forks source link

Reporting Good Decision Ratio #26

Open kdchin opened 9 months ago

kdchin commented 9 months ago

Hi!

I was wondering if there was an easy way of reporting the good decision ratio. I see that the existing behavior already reports byte miss ratio, and was wondering how hard it would be to also report the good decision ratio, and any guidance/pointers to particular files to look at to do so. Also, is segment_window or real_time_segment_window the Belady boundary? How would I change that parameter when running LRB on a trace?

Much thanks! -Kyle

sunnyszy commented 9 months ago

Hi - the good decision ratio needs some manual calculation. You can check the logging flag here: https://github.com/sunnyszy/lrb/blob/master/include/webcachesim/caches/lrb.h#L45. And the calculation method is in the paper.

segment_window and real_time_segment_window are not Belady boundary. They are used to control the granularity of logging aggregated misses/hits.

kdchin commented 9 months ago

thanks! ok so how would I adjust the belady boundary? (I can change the static values in the code, I just didn't see it as a parameter in the CLI).

sunnyszy commented 9 months ago

Hi you maybe mix belady boundary and memory window. The first is only for analysis purposes and not adjustable. The second is adjustable and used in LRB.

On Sat, Dec 16, 2023 at 11:35 PM Kyle Chin @.***> wrote:

thanks! ok so how would I adjust the belady boundary? (I can change the static values in the code, I just didn't see it as a parameter in the CLI).

— Reply to this email directly, view it on GitHub https://github.com/sunnyszy/lrb/issues/26#issuecomment-1859062146, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXQ675VYT4K5M3WU5YRIT3YJ2ODRAVCNFSM6AAAAABAYAJQHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGA3DEMJUGY . You are receiving this because you commented.Message ID: @.***>

-- Zhenyu