Usually SGE will find out the number of processors and assign "slots"
for it. You can increase/decrease the number of slots in the SGE
central configuration. You can also create a queue and set the number
of slots for all machines in the queue configuration.
The fastest option is probably NFS. Over gigabit I can get up to 4
streams of 300 Mbps (NFS server has dual gigabit and FibreChannel
storage) when your TCP stack is properly optimized. With Kerberos
authentication it's fairly secure but you shouldn't share it outside
your subnet, Kerberized NFS might be hard to set up and requires
correct DNS configurations. If you go with plain NFS you should
properly firewall and limit the NFS shares per IP, squash root etc.
There are guides out there that go in great detail on how to do it.
SMB is very slow (peaks at 12 Mbps per node) and there is no way to
make it any faster (I tried).
Evi Vanoost
[log in to unmask]
(585) 275-4549
On May 20, 2009, at 10:52 AM, Jiří Keller, M.D. wrote:
> Dear SGE experts in the list,
> I am setting up an FSL SGE cluster. While setting it up I came
> accross two major problems their solution is probably trivial for
> advanced SGE user, ut not for me.
> 1) how to set the numbre of cores in each machine in grid ? I am using
> mainly the queue long, but by default it uses 1 "thread"
> 2) what is the best(=fastest but reasonably secure?) way to share data
> between nodes ?NFS ? SMB ? Something else ?
>
> thank for answers
> George
>
|