3 ms·
Performance is going to be pretty bad with all of those re-executions, logging of state and so on.
by akuma73 12y ago
Performance is going to be pretty bad with all of those re-executions, logging of state and so on.
- seanmcdirmid 12y agoYes and maybe not. One optimization we perform now is to have a slow-path replay that does book keeping: logging updates, tracing dependencies, and performing dynamic type checks. But during this slow-path, a fast-path replay is generated that just re-executes the code while keeping book keeping constant (so no book keeping overhead), which is applicable if values just change slightly (e.g. in a physics simulation). See the paper for more details.