JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF

The open source
grid computing
solution

 Home   About   Features   Download   Documentation   On Github   Forums 
November 21, 2019, 07:29:49 AM *
Welcome,
Please login or register.

Login with username, password and session length
Advanced search  
News: New users, please read this message. Thank you!
  Home Help Search Login Register  
Pages: [1]   Go Down

Author Topic: client or job  (Read 2958 times)

nabilasbi

  • JPPF Master
  • ***
  • Posts: 29
client or job
« on: August 07, 2012, 01:56:52 PM »

I need your opinion about an issue in integration JPPF with my project,
A website that will be able to submit new programs to be run in the grid, with id.
The job will run on nodes in idle mode only, the driver will run the jobs in the order they were submitted to the system.
The job will use ftp server in running the task.
On job completion an email notification will be sent to the student.

My question is:
Is it the best practice is to create client per student program or new job per program ?
Logged

lolo

  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2257
    • JPPF Web site
Re: client or job
« Reply #1 on: August 08, 2012, 06:53:38 AM »

Hi Nabil,

It is generally recommended to only have a single JPPF client in your application. So in this case, I believe it would scale much better to have a job per program.
Also, if you have multiple users of your application that submit jobs concurrently, you might want to use, in your client, a pool of connections to the JPPF driver instead of a single connection.
To configure connection pools, please refer to the related documentation.

I hope this helps.

Sincerely,
-Laurent
Logged
Pages: [1]   Go Up
 
JPPF Powered by SMF 2.0 RC5 | SMF © 2006–2011, Simple Machines LLC Get JPPF at SourceForge.net. Fast, secure and Free Open Source software downloads