Hi Ajinkay, In Airavata we use Java Executor Services comes with java concurrency package for thread management, so we have delegate thread creation and management to Java instead of doing it all by ourselves. To be specific we used Fixed ThreadPool Executor inside Airavata. There are both good and bad in Thread vs Processes. If we use processes to run this local jobs then you have to manage process creation and deletion all by yourself anyway it is not a good practice to write long running synchronous jobs so we can assume these synchronous jobs are small in execution time.
Thanks, Shameera. On Thu, Sep 29, 2016 at 2:36 PM Ajinkya Dhamnaskar <[email protected]> wrote: > Hello All, > > For local provider I was exploring different ways to submit and get the > job done. As, it is a local provider we need not to have monitoring system > in place, simply forking a job on different thread should serve the > purpose. > > But, to do so we need to keep investigation that thread. In my opinion, > ProcessBuilder in java would be handy in this case or if you have any other > suggestions please do let me know. > > Just want to know and use if there is any better way to this. > > Thanks in anticipation > -- > Thanks and regards, > > Ajinkya Dhamnaskar > Student ID : 0003469679 > Masters (CS) > +1 (812) 369- 5416 > -- Shameera Rathnayaka
