in reply to having a container on perl VMs is good ?

Are you looking for threads?

If you want to have a central thing for keeping values across interpreters, look at a database, memcached or Redis maybe?

I'm not sure what problem you are trying to solve.

  • Comment on Re: having a container on perl VMs is good ?

Replies are listed 'Best First'.
Re^2: having a container on perl VMs is good ?
by xiaoyafeng (Deacon) on Nov 11, 2022 at 09:52 UTC
    basically, what I mean is multi interpreters is running on one process.

    If you want to have a central thing for keeping values across interpreters, look at a database, memcached or Redis maybe? I'm not sure what problem you are trying to solve.

    multi interpreters on one process have many advantages: 1. all the way you point out has data copy, 2. real threads on windows but not fork-like one.


    I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction

[reply]

      If you want multiple interpreters running in one process, that is what threads gives you. See also threads::shared, and also Thread::Csp for a more shared-nothing approach.

[reply]

In Section Seekers of Perl Wisdom