Haha, thanks, I know how you feel!
Ok, gotcha, so this value should be the number of cores and amount of RAM for the selected compute node type.
I guess it might make more sense to use the
smp PE rather than the
mpislots PE if none of the ClusterFlow jobs make use of MPI (ref: http://docs.alces-flight.com/en/stable/sge/sge.html#running-multi-threaded-jobs) – there’s no guarantee that jobs submitted to the
mpislots PE won’t be distributed across multiple nodes while the
smp PE enforces this. However, note:
Memory limits are enforced per CPU-core-slot; for example, if your default memory request is 1.5GB and you request -pe smp 4, your 4-core job will be allocated 4 x 1.5GB = 6GB of RAM in total.
Does ClusterFlow calculate and provide a
-l h_vmem value? I ask because, given the above, when using the
mpislots PEs this value would need to be “total amount of RAM needed for the job / number of slots requested”.
Yup, I don’t see any reason why not.
Naming things is one of the two hardest computer science problems!