Splitting Object Memory (was Re: [squeak-dev] My own Squeak direction)

Jecel Assumpcao Jr jecel at merlintec.com
Tue Nov 17 15:59:05 UTC 2009


Bert Freudenberg wrote:
> On 17.11.2009, at 04:18, K. K. Subramaniam wrote:
> > The object memory has old/new areas, but the image is still a binary monolith. 
> > As solid-state storages take hold, the cost of redundant writes will keep 
> > rising. Is anyone looking at options where an image is a folder of files 
> > instead of a single file?

I suggested that a couple of messages back in this thread.

> I'd love to have even a simple version of this. E.g., split the image into just two
> parts. Sort-of like VW's perm space (which is not garbage-collected ever) which
> would be the "base-image", plus all the rest in a second image file. This would
> allow to share a base image and a differential image in a similar fashion as we
> have a sources and a changes file. A regular save would just save the non-permanent
> part of the object memory. 

Sure: http://wiki.squeak.org/squeak/584

-- Jecel




More information about the Squeak-dev mailing list