RSS RSS feed | Atom Atom feed

Sharing the virtual machine

This was an interesting session. Many details about how to increase performance and reduce the memory footprint were discussed. An example would be a single computer with multiple virtual machine's each running their own application. Each VM loading java.lang.String is wasteful and could be made better if multiple applications could run inside an MVM(Multitasking Virtual Machine). This concept is very similar to Operating System processes and threads. i.e. Creating a new process is an expensive, costly unit of work. Creating a thread within a process is relatively inexpensive unit of work. So the parallel is that a single MVM running multiple apps is more efficient like a multi-threaded operating system process. The downside to this is that if one app were to puke(warning: graphic technical term), it would take down the other apps with it. The presenter discounted this argument based on all the VM enhancements that are occuring. He did say that collocation could be achieved by running multiple MVM's on a single machine. This is a special case though.

Tags :


Re: Sharing the virtual machine

Do you have a link to this session?

Re: Sharing the virtual machine

There is a link if you have a login to JavaOne, but I cannot link to it directly. They would probably have issues if I copy/pasted the content in my blog as well. Sorry!

Re: Sharing the virtual machine

Was he saying that they would all be running under the one process? What would happen when you need to kill off one of them?

Re: Sharing the virtual machine

If you are asking, "if you have multiple MVM's running on a machine, are they running with the same os process?" The answer is no. Each MVM would be running as a separate process. Each Application within a single MVM would be running in a single process.