renatahodovan / picire / 5548461824

93%

push

github

Cache optimizations (#30)

The following optimizations aim at enhancing the memory usage of
the cache. They may also have a positive effect on the running
time of the cache access operations because of the reduced size of
the cache.

- Adding failing configurations, i.e., interesting test cases to
  the cache is superfluous, since once a fail is found, all
  subsequent configurations during the reduction will be smaller.
  So, this new cache entry would not generate a hit afterwards.
- When a failing configuration is found, then all cache entries
  that belong to larger configurations should be evicted, since all
  subsequent configurations during the reduction will be smaller.
  So, these old cache entries would not generate hits afterwards.
- When using content caching, storing a hashed version of the
  content instead of the content itself should be sufficient. Cache
  collisions are expected to be rare and even if they happen, they
  do not violate the correctness of the algorithm, they may only
  cause suboptimal, i.e., non-minimal results (assuming that
  failing configurations are not added to the cache).

Co-authored-by: Dániel Vince <vinced@inf.u-szeged.hu>

92 of 92 new or added lines in 3 files covered. (100.0%)

711 of 807 relevant lines covered (88.1%)

0.88 hits per line