tfesenbecker / lapis

Lapis is an adaptable, performant, and interactive scheduling simulator
MIT License
0 stars 0 forks source link

Design decision in hitrate based caching: should input files be provided file-wise or job-wise? #13

Open tfesenbecker opened 4 years ago

tfesenbecker commented 4 years ago

In the current implementation either all or no input files of a job are provided by a cache. This is based on the assumption that caching/cache eviction policies would most likely handle the input files of a job in a similar manner. This design decision should be discussed when deciding on future simulation scenarios. E.g. if random caching/ cache eviction policies are used this assumption is invalid.

tfesenbecker commented 4 years ago

In this case the evaluation whether a file is cached should be done for every file instead of once for a job