Hello, I would like to confirm whether the following observation is correct: Is the gem5 RISC-V simulation of riscv-ubuntu-20.04-boot approximately 30 times slower than the equivalent workload for x86 and aarch64? Or could there be an error in my setup?
Scenario: I am booting a full-system simulation on all three platforms (RISC-V, x86, and ARM) using their respective gem5 resource workloads for Ubuntu 20.04. I'm utilizing an ATOMIC processor and 4GB of memory for these tests. To measure performance, I am timing how long it takes to reach the m5 exit point. I have used the same custom script for all platforms. While the x86 and ARM platforms take less than 4 minutes to boot, the RISC-V simulation takes around 110 minutes. I also tried running the sample configuration riscv-ubuntu-run.py, but changed the processor to ATOMIC. The boot time remained equally lengthy. For comparison, the riscv-fs.py script (which uses riscv-disk-img, a different image) boots in under 4 minutes. My testing environment is an x86 i9-13900K system with 64GB of memory, running Ubuntu 22.04.3 LTS. I've tested with build/ALL/gem5.fast and build/RISC-V/gem5.fast, both built from gem5 stable version 23.0.1.0. Is the RISC-V simulation inherently slower, or is the Ubuntu image for RISC-V more resource-intensive than those for ARM and x86? Best regards, Daniel
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
