Even the ramdisk would be an enormous slowdown because you’re putting the CPU registers/stack all the way in ram, and because all your memory accesses are being passed through some sort of heavy filesystem api. Whether or not that matters depends on what you’re doing, though.
I think the bigger thing is that in order to have this time travel feature, you’d have to save a copy of the history of every register somewhere in memory or somewhere on disk. Every ‘i’ in every for loop needs to be cached somewhere. There’s gotta be a huge memory footprint, although I’d be excited to see how far you could take this.
Looks kind of cool, but won’t you be reading and writing to disk an awful lot?
Could be run on a ramdisk when you’re not too worried about power failures and such.
Even the ramdisk would be an enormous slowdown because you’re putting the CPU registers/stack all the way in ram, and because all your memory accesses are being passed through some sort of heavy filesystem api. Whether or not that matters depends on what you’re doing, though.
I think the bigger thing is that in order to have this time travel feature, you’d have to save a copy of the history of every register somewhere in memory or somewhere on disk. Every ‘i’ in every for loop needs to be cached somewhere. There’s gotta be a huge memory footprint, although I’d be excited to see how far you could take this.