1 / 22

Yeti Operations

Yeti Operations. Introduction and Day 1 Settings. Rob Lane HPC Support Research Computing Services CUIT hpc-support@columbia.edu. Topics Yeti Operations Committee Introduction to Yeti Rules of Operation. Yeti Operations Committee Determines cluster policy

ulema
Télécharger la présentation

Yeti Operations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Yeti Operations Introduction and Day 1 Settings

  2. Rob Lane HPC Support Research Computing Services CUIT hpc-support@columbia.edu

  3. Topics Yeti Operations Committee Introduction to Yeti Rules of Operation

  4. Yeti Operations Committee • Determines cluster policy • In the process of being set up • In the meantime we need a policy for day 1 of operations

  5. 2. Introduction to Yeti

  6. Final Node Count

  7. Meet Your New Neighbors

  8. Group Shares

  9. Other Groups • Renters • Free Tier • CUIT

  10. Rules of Operation Job Priority Job Characteristics Queues Guaranteed Access

  11. Job Priority • Every job waiting to run is assigned a priority by the scheduling software • The priority determines the order of jobs waiting in the queue

  12. Job Priority Components • Group’s share vs. recent usage • User’s recent usage • Other factors

  13. Recent Usage • What does “recent” mean? • It’s configurable • Yeti’s setting: 7 Days

  14. Job Characteristics • Nodes and cores • Time • Memory

  15. Job Queues (subject to change)

  16. Guaranteed Access • New mechanism • Subject to review by Yeti Operations Committee • We’re going to try it out in the meantime

  17. Guaranteed Access • Groups have each been assigned systems • Group jobs get priority access to their own systems • “Guaranteed Access” means there will be a known maximum wait time before your job starts running

  18. Guaranteed Access Example • The group astro owns the node Brussels • Only two types of jobs will be allowed on Brussels • Astro jobs • Short jobs

  19. Job Queues (subject to change)

  20. Guaranteed Access Debate • Good because researchers have guaranteed access rights to nodes • Bad because long jobs lose access to many nodes

  21. Thanks! Comments and Questions? hpc-support@columbia.edu

More Related