microsoft / microsoft/pai

prerequisite: auto save checkpoint

Open
#5,339 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pai-dev
Dominant language
JavaScript
Stars
2.7k
Forks
554
Avg merge
20h 42m
Merged PRs (30d)
14

Description

Motivation

Jobs fail at different stages.
The users will have to retrain their models from scratch if they fail to save the checkpoints / result files properly.
If they have a folder which will be saved automatically, it will be easier for users to manage these data.

Design

  • two prerequisite
    • mount-autosave-folder: mount cluster storage to task container
    • auto-save: copy check-point folder to mount point
  • cluster requirement:
    • cluster level storage
  • schema
prerequisites:
  - type: data
    name: mount-autosave-folder
    plugin: com.microsoft.pai.runtimeplugin.cmd
    mountPoint: /mnt/auto-save
    callbacks:
       - event: taskStarts
        commands:
          - mount  cluster-data-path ${mountPoint} 
  - type: autosave
    requires: mount-autosave-folder
    name: autosave-results
    plugin: com.microsoft.pai.runtimeplugin.cmd
    path: /user/experiments/check-points
    callbacks:
       - event: taskStarts
        commands:
          - apt update 
          - apt install rsync
      - event: taskEnds
        commands:
          - rsync ${path} /mnt/auto-save

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing how prerequisites, runtime plugins, taskStarts, and taskEnds callbacks are handled, then inspect how cluster-level storage is configured. Done should support mounting cluster storage and copying the specified checkpoint or result path there when the task ends.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
infrastructure, machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.