Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Java, supposing you want to run a task in its own heap space (e.g. so that it can crash with an out of memory error without affecting the rest of your program), you can use Runtime.exec to load the JVM and the relevant byte code files from the file system and redo all the work that needs to be done to start up a Java program from scratch.
This is somewhat high overhead, if the tasks you want to run are fairly fine-grained. Is there any lower overhead way to do it?
Since you’d be anyways doing interprocess communication, is looking into RMI an option for you? With RMI daemon, you can have pooled processes to which you can submit jobs and get back results. This also relieves you of manually managing spawning VM’s etc.
Or look into a job queue based solution in which the main VM creates job packets and dumps them on the queue which is monitored by one or more processes. Anyways, AFAIK, the most fine grained way of doing these is not spawning VM’s on demand.