We've been using memory cgroups for jobs for several years, and CPU sets for a year. We haven't had any problems, and our users are much happier too, since we can enforce on actual used memory rather than address space, and jobs are locked to only the CPUs they request.
We're running UGE 8.3.1p7 and CentOS 6.9. On Thu, Feb 15, 2018 at 11:28:58AM -0600, Calvin Dodge wrote: > While the help we received from this and other gridengine lists helped > us resolve the issue of jobs being mysteriously killed, we've been > asked to look into converting the customer's SGE cluster, using > cgroups for job management. > > The cluster is running gridengine 8.1.9, on Linux kernel > 3.10.0-514.el7.x86_64 (Centos 7.3.1611). Can anyone comment on the > reliability of using cgroups for job management in that environment? > I ask because I ran across some web pages which stated that for some > versions of gridengine and kernel this was a Bad Idea. > > Sincerely, > > Calvin Dodge > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users -- -- Skylar Thompson ([email protected]) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
