Hi Benjamin, Benjamin Redling <[email protected]> writes:
> Hi, > > Am 31.05.2017 um 10:39 schrieb Loris Bennett: >> Does any one know whether one can run multinode MATLAB jobs with Slurm >> using only the Distributed Computing Toolbox? Or do I need to be >> running a Distributed Computing Server too? > > if you can get a hand on the overpriced and underwhelming DCS (at least > up to the 2016b Linux variant the mdce service neither has startup > scripts with LSB tags, nor systemd units; only the very first annoyance), > the following might be a consolation: > " > Access to all eligible licensed toolboxes or blocksets with a single > server license on the distributed computing resource > " > https://www.mathworks.com/products/distriben/features.html > > > (We currently use DCS without Slurm integration and thous are bad > citizens considering the license pool we have to share. > But running DCS without scheduler integration is bad in many ways. e.g. > proper security levels don't cooperate with plain LDAP, default security > runs job as root [hello, inaccessible NFS shares] so it seems users > either start single node parallel jobs apart from DCS or DCS-Slurm > integration is mandatory and you get all the benefits -- license count, > security level, multi-node) Thanks for the information. Currently we only have one user wanting to run jobs on more cores than we have on individual nodes and I also need to check how his code scales before shelling out for DCS. We are also bad citizens in that we allow some interactive and batch usage of MATLAB licenses from the same pool. To stop jobs failing because the licenses are all in use, jobs have to specify a reservation containing the available licenses. This is updated regularly by a cron job which parses the output of the license manager. It works, but it's a bit of a nasty hack. Cheers, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
