On Wed, Jun 6, 2012 at 12:03 AM, Joseph A. Farran <[email protected]> wrote: > Ok. I was not sure if OGE had a default way of telling it the Parallel > name to use if none was given.
I think the client-side JSV way is the best way to pick the default PE... unless Reuti or others have other better ways. (There's always more than 1 way to do things in Grid Engine.) > From what I can tell so far with OGE > (correct me if I am wrong) compared to Torque which is where I am coming > from, the Parallel Environment is just a tag to define some parallel configs > such as how to allocate cores (slots), etc. With Torque you request both > nodes & cores in your job script, so you can slice and dice fairly easily. I understand what you mean - eg. the nodes/ppn, procs parameters in Torque and the -R "span[ptile=<value>]" in LSF are more flexible. As I mentioned before, Grid Engine PEs have a lot more than just parallel configs - PE affects scheduling, tight or non-tight integration (which then affects the handling of launching slave tasks), and the actual execution of the PE (start_proc, etc). It is a very heavy interface, and we understand the issue. However, we can't just change the code overnight - we need more developers if we were to clean up all the non-straightforward interfaces in Grid Engine (and trust me, the PE interface is not that bad!). Rayson > > If anyone has a links / references on tips for transitioning from Torque to > OGE, please post. > > Best, > Joseph > > > > > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
