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
  • batsim
  • batsimbatsim
  • Issues
  • #53
Closed
Open
Issue created Feb 06, 2018 by Millian Poquet@mpoquetOwner

Test fewer_resources needs improvement

This test is hard to read and understand.

The tested scenario is the execution of one msg_par_hg profile without communication.
Only one profile is tested, that requires 4 executors. Different mapping are done.

#hosts cpu_load
1 (4)
2 (2,2)
3 (2,1,1)
4 (1,1,1,1)

In this case, the execution time is expected to be slowed down by a factor of max(cpu_load).
Making this explicit would be better than just writing the expected values in the test.

It would also be interesting to split this check by profile type, as this behavior is only expected for computation-only msg_par_hg profiles.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking