G'day xiaoyafeng,
Unfortunately, this seems to fall into "XY Problem" territory: you've indicated that you think "management container" is a solution (Y); you haven't specified what problem (X) you want this to solve (except in a very general sense).
"... let perl having more power and better face on the modern multi-core environment."
That sounds like what MCE achieves. This has a lot of documentation: it's nicely laid out, and has many examples (including a specific MCE::Examples page), but will still require a fair bit of reading. A couple of suggestions that seem to fit with what you're asking: "GLOBALLY SCOPED VARIABLES AND MCE MODELS"; "MCE->gather()".
"... container on perl VMs ..." [from title]
I was unsure what you meant by this. For $work, I've set up a VM in which I run applications that use Docker images with 15 different Perl versions. Each image uses code & data specific to its own Perl version but can also access more general, shared code & data from the VM. Perhaps this is closer to what you want.
There's also "perlipc - Perl interprocess communication". That may provide some suggestions that might be of use to you.
— Ken
In reply to Re: having a container on perl VMs is good ?
by kcott
in thread having a container on perl VMs is good ?
by xiaoyafeng
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |