This is weird; it never took me more than 20 seconds to generate a single
checkpoint in gem5.
I suspect most of the time is spent on draining the system.
Would you be able to debug which draining method is stalling the checkpointing
process?
Kind Regards
Giacomo
From: Hanhwi Jang via
I currently use ARM-KVM with gem5,
so reaching the point for checkpointing takes just a couple of minutes and
is not a problem.
Just writing a checkpoint takes 10 mins even on locally-mounted SSDs.
Before digging into the issue, I just wanted to know if this is normal.
Maybe I have to check my
On 11/14/2022 12:42 AM, Hanhwi Jang via gem5-users wrote:
Thanks for your reply.
Yes. I mean that; serializing all SimObjects and writing them on a disk.
Does the checkpoint latency depend on the workload behavior?
For GCC, the checkpoint takes around 10 mins for a single point,' but it takes
Thanks for your reply.
Yes. I mean that; serializing all SimObjects and writing them on a disk.
Does the checkpoint latency depend on the workload behavior?
For GCC, the checkpoint takes around 10 mins for a single point,' but it
takes 3 mins for MCF.
I am not sure this is normal.
Thanks,
Hanhwi
On 11/13/2022 1:24 PM, Hanhwi Jang via gem5-users wrote:
Hi everyone,
I recently returned to gem5 and tried to create SimPoints for SPEC and other workloads on ARM
architecture.
gem5 works great as usual, but I am curious why it takes 10~30 mins to write just a single
checkpoint. The
