Replaying a scenario in REVEN (i.e. generating the scenario’s resources) is a process mixing high IO and CPU usage. Estimating how long it will take highly depends on your hardware and what the VM is doing during the record of the scenario.
A basic and rough estimation with a i7-7700k and a SATA SSD is around 1 hour per billion of instructions to replay. But remember this a small time to wait before accelerated analysis!
So, how can you speed-up the replay?
- As the replay can take up to 4 threads on a CPU, a CPU with at least 4 powerful cores is recommended.
- As the replay highly depends on the IO, you should maximize the bandwidth and the latency of read/write operations.
- Make sure that
QUASAR_ROOTin the settings points to a directory using high IO storage.
- As the replay depends on the number of instructions to replay, limit unnecessary VM activity during scenario recording to minimize the overhead of the record: disable desktop graphical effects, disable unnecessary services, etc. See http://doc.tetrane.com/latest/Project-Manager/Workflow/Create-VM.html for more information.
- Avoid replaying resources if you know you won’t use them. For example if you won’t use the Strings feature, do not replay the corresponding resource.