![]() |
||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||
Using Multiple Job QueuesHaving multiple GridLink licences makes a GridLink farm more powerful in two ways: first, it allows you to use more CPU cores, which makes your jobs finish faster; second, it allows you to use multiple job queues, which makes your jobs start faster. When you have two job queues, if there's a distributable job started in one job queue already and you submit another job to the same queue, it has to wait until the previous one finishes. However, if you have a second job queue available, you can submit your job to the second queue and it will start immediately. The farm will be automatically split, and some resources will be released from the first job to run the second one. When you had only one job queue, the job submission was simple: all users submitted their jobs to the same job queue on the single master server. When you have two job queues, one question you may want to ask is: which job queue should each user submits his/her jobs to? You have 2 options to use these 2 job queues: 1. Allow All Users to Access Both Job Queues If you want to allow all users to access both job queues, you can achieve this in 2 different ways:
2. Designate Controllers to Users In the case that the farm is shared by two departments, for security reason, it would be preferable to designate one controller to users in one department, and designate one controller to users in the other department. While all of them will be able to utilize the whole farm, users in one department will not be able to view the remote jobs submitted from the other department. |
||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||