pegasus should pass a profile that indicates the multiplier factor / num of cores that a job requires as a classad to the submit files.

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • master, 4.0
    • Affects Version/s: master, 4.0
    • Component/s: Pegasus Planner
    • None

      We decided to have a pegasus profile called cores, that will allow user to indicate in the DAX how many cores a job required.

      Original Request by Mats as part of 472
      Currently, stampede considers all jobs to be single threaded. If a user runs multicore or MPI jobs, the stats comes out wrong. For example, if you run a 1 hour long 128 core job, stampede will still report the cumulative time of 1 hour. The correct answer would be 128 hours.

      On possible fix would be to add a "multiplier" to the schema so that each job can be scaled up based on core count.

            Assignee:
            Fabio Silva
            Reporter:
            Karan Vahi
            Archiver:
            Rajiv Mayani

              Created:
              Updated:
              Resolved:
              Archived: