Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • ng6 ng6
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • genotoul-bioinfo
  • ng6ng6
  • Issues
  • #73
Closed
Open
Issue created Sep 17, 2018 by Gerald Salin@gsalinMaintainer

problem with gzip 1.5 and 1.9 on the new cluster

after some hours of debugging, we found the 1.5 and 1.9 version of gzip implies problem with the server load. huge peaks (> 1000 of load average) were observed and reproduced in the case of massive jobs using system gzip (on the new slurm cluster). It was not observed with the sge cluster, using version 1.3.

installing 1.3 gzip version on the new cluster solved the problem, but we have to use get_exec_path("gzip") in the components instead of gzip command line

Assignee
Assign to
Time tracking