MQSim is a fast and accurate simulator modeling the performance of modern multi-queue (MQ) SSDs as well as traditional SATA based SSDs. MQSim faithfully models new high-bandwidth protocol implementations, steady-state SSD conditions, and the full end-to-end latency of requests in modern SSDs. It is described in detail in the FAST 2018 paper by Arash Tavakkol et al., "MQSim: A Framework for Enabling Realistic Studies of Modern Multi-Queue SSD Devices" (https://people.inf.ethz.ch/omutlu/pub/MQSim-SSD-simulation-framework_fast18.pdf)
in MQSim paper i had seen that fio generates the trace files but device number and address column is not generated in fio where can i find such a tool to do it. And Device Number is not used much in the code can i keep it random uniform #51
Hi @HrithikSampson,
The device number is found in many ASCII trace file standards. For example, in the UMASS specification for the storage traces, there is a column referred to as the Application Specific Unit with similar meaning. MQSim does not use this field for simulations but accepts it to prevent the need for adjusting ASCII trace files.
Regarding fio: we used this tool for real system benchmarking. However, for the simulation experiments, we used the synthetic workload generator in MQSim that replicates the behavior of a real device benchmarking tool.
HrithikSampson
commented
3 years ago
Hi @HrithikSampson, The device number is found in many ASCII trace file standards. For example, in the UMASS specification for the storage traces, there is a column referred to as the Application Specific Unit with similar meaning. MQSim does not use this field for simulations but accepts it to prevent the need for adjusting ASCII trace files. Regarding fio: we used this tool for real system benchmarking. However, for the simulation experiments, we used the synthetic workload generator in MQSim that replicates the behavior of a real device benchmarking tool.