Re: Alternative persistence system

On Oct 12, 2009, at 18:02, Charles Landau wrote:
> Kevin Reid wrote:
>> On Oct 12, 2009, at 5:58, Thomas Leonard wrote:
>>> The system does not scale well. When an object's state
>>> changes, the entire object graph has to be written out, which takes
>>> time
>>> proportional to the number of objects in the system (roughly 10 ms  
>>> per
>>> object on my machine), not to the number of changes.
>>
>> Due to E's requirements for consistency on revival, an entire vat
>> *must* be persisted as a unit. (Of course, if an application such as
>> yours has weaker requirements you can use an alternate system.)
>
> That does not imply that the implementation must take time  
> proportional
> to the size of the vat. KeyKOS and CapROS only write out objects that
> were changed since the last checkpoint.

KeyKOS and CapROS use orthogonal persistence, which greatly simplifies  
the problem.

-- 
Kevin Reid                                  <http://switchb.org/kpreid/>