4 ms·
Conceptually similar in that you can decide after-the-fact what state you want to see. But Time Travel Debugging applies that to everything in the program, not
by mark_undoio 3y ago
Conceptually similar in that you can decide after-the-fact what state you want to see.
But Time Travel Debugging applies that to everything in the program, not just log statements - all function calls, variables, memory locations, etc can be reconstructed after the fact without having to log them explicitly.
- mark_undoio 3y agoOh, and regarding how long - it depends how long it takes to fill the circular buffer of non deterministic behaviour. Serious compute bound workloads can run days with a gigabyte of non deterministic event log. Serious IO bound workloads burn it much faster. For a rule of thumb, think of it consuming a few MB per second, so the length of the time travel is limited by how much of that you can store.