I was looking over safe_vault code and conversing with some interesting individuals on the forums and it seems from the codebase that it would not be so tricky to add a memory persistence model to SAFE in the same way that the disk operations work (i.e create an alternative chunk_store to begin with which is in-memory specialised).
What I envision is two distinct types of memory, Transient and Persistent, where the persistent model is introduced initially for those who want a faster distributed disk array. Persistent memory functions similar to the way disk persistence works except it uses main memory as a resource rather than disk, similar to memcache or AcidState. Transient memory would be memory used for ‘compute’ runs once the CPU becomes a resource.
I’ve thought about the CPU as a resource but have not come up with a good enough model yet which is why I’m trying to focus on memory instead of a general compute model.
In terms of value and how it would affect farming, once could draw a comparison of the price per mb of HDD space and main memory and use that as a basic guideline to begin with.
Would it be worthwhile if I work on creating a more comprehensive RFC for this?