demo of what checkpointing plugins might look like #3535

this test checks that memoization works with all configs test design: that's not necessarily true in future but it should be now. in future perhaps a memoizer option would be "NoMemoizer" which would not do *any* memoization, not even in-memory-only? but I think its ok to not do that for now and i think its ok to require that a memoizer always does actually do memoization at a memory level (so you can't avoid it...)

this test checks that checkpoint dir exists checkpoint_1 checks that files exist within the checkpoint dir

and is more reusable when it isn't this isn't the only way to make a hash though. and hashing isn't the only way to compare checkpoint entries for equality.

goal: results should not (never? in weak small cache?) be stored in an in-memory memo table. so that memo table should be not present in this implementation. instead all memo questions go to the sqlite3 database. this drives some blurring between in-memory caching and disk-based checkpointing: the previous disk based checkpointed model relied on repopulating the in-memory memo table cache... i hit some thread problems when using one sqlite3 connection across threads and the docs are unclear about what I can/cannot do, so i made this open the sqlite3 database on every access. that's probably got quite a performance hit, but its probably enough for basically validating the idea.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

demo of what checkpointing plugins might look like #3535

demo of what checkpointing plugins might look like #3535

Commits on Aug 22, 2024

demo of what checkpointing plugins might look like #3535

Are you sure you want to change the base?

demo of what checkpointing plugins might look like #3535

Commits on Aug 22, 2024