The forcite module works good with torque.
But when I submit a Sorption job which don't support parallel, it occupied 40 nodes and 40cores, not just 1.
So is it a issue of the config of torque or a bug of MS?
The forcite module works good with torque.
But when I submit a Sorption job which don't support parallel, it occupied 40 nodes and 40cores, not just 1.
So is it a issue of the config of torque or a bug of MS?