[Vm-dev] Multi-Image Sista VM?

[Robert]

Hi ya, Tim,

I had to mull this over a little. In my use case, I believe that each 
core is running its own event loop inside its own memory. Objects are 
not shared. Yet, there is a use case to migrate objects to different 
event loops. Doing so efficiently may provide an opportunity to do 
heuristics with performance and tune the threads within 1 process. I 
think it opens another dimension in performance optimization that would 
allow some sort of JIT compiler moving actors around. A) Actor Mobility. 
Plus it would be B) totally cool!!! I mean completely! + 1,000 coolness 
factor.

Your thoughts?

K, r

On 5/1/20 5:32 PM, tim Rowledge wrote:
>
>
>
>> On 2020-05-01, at 11:59 AM, Clément Béra <bera.clement at gmail.com> wrote:
>>
>> The Hydra VM from Igor was doing exactly that.
>>
>> The Actor model in Newspeak is also somewhat similar to that, though part of the image is shared between threads.
> I'm not sure what benefit is anticipated by running multiple images on one vm.
>
> The VM executable is not terribly big, so you don't save a great deal of memory and any sensible OS is likely to be able to share the static code pages at least. For a Cog VM quite a lot of space for the caches and translated code needs to be per-image, so you wouldn't save there.
>
> A VW-like permspace that is treated as read-only can also be shared of course.
>
> So what would the advantages be?
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Design simplicity: It was developed on a shoe-string budget.
>
>
-- 
Kindly,
Robert