1. 25 Jul, 2013 1 commit
  2. 23 Jul, 2013 4 commits
  3. 22 Jul, 2013 1 commit
  4. 18 Jul, 2013 1 commit
  5. 16 Jul, 2013 2 commits
  6. 11 Jul, 2013 2 commits
  7. 10 Jul, 2013 2 commits
  8. 09 Jul, 2013 4 commits
  9. 08 Jul, 2013 1 commit
  10. 06 Jul, 2013 2 commits
  11. 05 Jul, 2013 2 commits
    • John Thiltges's avatar
      Correction to memory limit calculation for mem per cpu with threads · 0d537d32
      John Thiltges authored
      When using ThreadsPerCore > 1, it appears that DefMemPerCPU is being
      scaled by slurmctld, but not by slurmd/slurmstepd.
      
      For example, we set ThreadsPerCore=2 and DefMemPerCPU=100. Running a
      single core job, we would expect two threads to be allocated and AllocMem
      on the assigned node to increase by 200MB. scontrol reports that AllocMem
      increased by 200MB, but the task/cgroup plugin only sees 100M of RAM.
      
      It looks like the problem may lie in common/slurm_cred.c:format_core_allocs().
      The function counts the job/step cores and multiplies the mem_limit's,
      but it does not scale the CPU count like in slurmd/slurmd/req.c:_check_job_credential().
      See bug 309
      0d537d32
    • jette's avatar
  12. 28 Jun, 2013 3 commits
  13. 26 Jun, 2013 2 commits
  14. 25 Jun, 2013 3 commits
  15. 24 Jun, 2013 1 commit
    • jette's avatar
      Modify slurmctld locking to improve performance · ba58d59c
      jette authored
      Under very heavy load with many thousands of batch job submissions
      or job signals, the write lock can be held for very long periods of
      time preventing job scheduling, squeue response, etc. This code
      inserts a timing break to permit other functions to get the locks.
      ba58d59c
  16. 21 Jun, 2013 4 commits
  17. 18 Jun, 2013 2 commits
  18. 12 Jun, 2013 1 commit
  19. 10 Jun, 2013 1 commit
  20. 07 Jun, 2013 1 commit