Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • batsim batsim
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

La mise à jour du service Gitlab est terminée. Merci aux collègues du service de production de la DSI qui ont réalisé cette opération qui outre les aspects évolution du logiciel nous a permis de faire le nécessaire face à des failles de sécurité.
Les principales releases notes concernant cette montée de version sont disponibles ici :
https://about.gitlab.com/releases/2023/01/22/gitlab-15-8-released/
https://about.gitlab.com/releases/2022/12/22/gitlab-15-7-released/
https://about.gitlab.com/releases/2022/11/22/gitlab-15-6-released/

  • batsim
  • batsimbatsim
  • Issues
  • #4
Closed
Open
Issue created Feb 16, 2017 by Millian Poquet@mpoquetOwner0 of 3 checklist items completed0/3 checklist items

Batsim resources unit should be core instead of host

For multiple reasons:

  • Most of the existing workloads (SWF) contain core base resource request
  • Node level is detailed enough to see core based allocation when using time sharing
  • On current HPC centers, the request of resources is done by core (even if is ceiled depending on the number of core per nodes because there is no time sharing)
  • Batsim workload that contains node resource requests are not portable across platforms especially for SMPI applications that are modeled at the core level

The list of feature and changes we need to implement this:

  • change Batsim output to cores level (interval set of resources at core level) while keeping node information (and at the node level to be able to keep heterogeneity information).
  • support new resource requests like nb_core and nb_host and remove the ambiguous nb_res.
  • make the mapping work at core level (not sure of this... @mpoquet?)
Edited Aug 31, 2021 by Millian Poquet
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking