THUDM / THUDM/slime

[Question] qwen3.5-9b 128k上下文下的sft设置该怎么做

Open
#1,802 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
8.5k
Forks
1.3k
Avg merge
5h 36m
Merged PRs (30d)
22

Description

Your Question

cp无效的情况下,不知该如何设置了

What I've Tried

SFT_ARGS=(
--rollout-function-path slime.rollout.sft_rollout.generate_rollout
--prompt-data "${SFT_DATA}"
--input-key messages
--rollout-shuffle
--num-epoch 3
--rollout-batch-size 32
--global-batch-size 32
--loss-type sft_loss
--calculate-per-token-loss
--disable-compute-advantages-and-returns
--debug-train-only
)

PERF_ARGS=(
--tensor-model-parallel-size 4
--sequence-parallel
--pipeline-model-parallel-size 1
--context-parallel-size 1
--expert-model-parallel-size 1
--expert-tensor-parallel-size 1
--recompute-granularity full
--recompute-method uniform
--recompute-num-layers 1
--use-dynamic-batch-size

)

OPTIMIZER_ARGS=(
--optimizer adam
--lr 1e-5
--lr-decay-style cosine
--min-lr 1e-6
--lr-warmup-fraction 0.1
--weight-decay 0.1
--adam-beta1 0.9
--adam-beta2 0.95
)

Environment (if relevant)
  • slime version:
  • Python version:
  • PyTorch version:
  • CUDA/ROCm version:
  • GPU type and count:
  • OS:
Additional Context

No response

Pre-submission Checklist

Contributor guide

Open the contributing guide

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

Start by reviewing the SFT_ARGS and PERF_ARGS shown in the issue, then consult the linked documentation and FAQ for context-parallel and SFT configuration. The issue would need complete environment details and a reproducible explanation of what “cp” failing means; done would be a documented, validated configuration for this 128k SFT setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.