[Vm-dev] Re: [squeak-dev] re: Image Segment semantics and weakness
bert at freudenbergs.de
Wed Oct 22 16:16:30 UTC 2014
On 22.10.2014, at 08:47, Craig Latta <craig at netjam.org> wrote:
>> So it seems we agree that the key and good part of ImageSegment is
>> that one, swapping out, but not as a general object graph serializer.
> Even for swapping out objects, I think putting them in their own
> normal object memory is a better idea, since object memories can be
> minimal and small. This lets you perform more sophisticated reasoning
> about what to do when class formats change between swap-out and swap-in
> (as well as other meta-operations).
That's a different thing. Swapping is strictly about cutting up a single image into multiple segments. Proper mutation code would have to walk the whole object memory, meaning it needs to swap in all segments in turn. Which fortunately is extremely efficient, but likely still hairy enough that we're not actually using it given today's abundance of main memory. It might, however, still make a lot of sense e.g. as a deployment mechanism on mobile platforms, which still are severely memory-limited. If used strictly for deployment you don't have to worry about mutation.
- Bert -
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4142 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20141022/803b1c3c/smime.bin
More information about the Vm-dev