Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Cache, apply cache, and store serialised
The data should then be retrievable by reading the serialised
By serialising and storing in the scene, we gain two things.
Considering that caches can grow large, in the megabyte range, we are likely looking at a significant file size increase. The good news is that, once the cache nodes are removed, the data is removed with it. In this way I think we will find a good place to start looking into making optimisations.
When working on simulations, it's important to relate a cache to how it was made(1).
Traditionally, this would have required great discipline, in saving a scene for each cache made and somehow associating the files to the scene which created it, typically by name. E.g.
Loosing track of the source scene, or not having one in the first place, has disastrous consequences, in that you can no longer perform tweaks to the version they may like the most.
With memorycache, each cache can preserve the exact circumstance with which it was created without user intervention, and automatically maintain a link between the two.
(1) the reason being that you might be requested to continue working on v65, even though v68 is your latest.