Skip to content

Error when reading new VBA #6

Description

@zjsea

I am trying to run Sibyl with msr-cambridge1-sample.csv (http://iotta.snia.org/traces/block-io/388). I replaced the storage drivers with dummy code that calls time.sleep() to simulate latency.

There is an error with the read() function in hybridstorage.py when a new VBA is being read (line 110 of msr-cambridge1-sample.csv). The read() function only handles the case when VBA is in self._mapping_table.index. This means the VBA must have been written by Sibyl before.

if VBA in self._mapping_table.index:

If the VBA is not in self._mapping_table.index, the latency defaults to 0. This causes a zero division error when computing the reward because self._current_perf is 0.

reward_perf=(0.1/self._current_perf)-self._hybrid.numEvicts**0.09

Please advise how should read requests for new VBA be handled. The latency should not default to 0. Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions