2007/12/26, Igor Stasenko <siguctua at gmail.com>:
> On 25/12/2007, stephane ducasse <stephane.ducasse at free.fr> wrote:
> > >>
> > > There is more and more pressing matters, because we are standing at
> > > rising multi-core era. So, we need tools for fully utilizing their
> > > powers.
> >
> > yes!
> > So what would be a typical set up of multiple images from your
> > perspective?
> >
> There can be a wide range of deployment models, depending on intents.
> As i said, its a general purpose VM, and therefore things you can do
> with it depends on your imagination :)
>
> For Seasiders, there now a good perspectives to have a single 'main'
> image, which accepts incoming connections, and do load-balancing
> between smaller images which do all dirty work.

How would that work? How would you pass a request to a different
image? How would it return the response? How would you keep the images
in sync (deploy code to all the images)? I still feel that for Seaside
one Image with multiple native threads would be the best option.

Cheers
Philippe

> You could have much finer control on things comparing to running
> multiple squeak processes.
>
> I think, that Andreas having own ideas how to use new VM, and i think
> it's better ask him to describe where it will be used.
>
> But things are more or less the same: distribute the tasks between
> multiple images, making them performing in parallel.
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
>