Skip to content

[megatron] feat: script of qwen3vl 235b - #3799

Merged
ISEEKYAN merged 1 commit into
verl-project:mainfrom
ISEEKYAN:mcore_qwen3vl235b
Oct 17, 2025
Merged

ISEEKYAN merged 1 commit into
verl-project:mainfrom
ISEEKYAN:mcore_qwen3vl235b

Conversation

@ISEEKYAN

Copy link
Copy Markdown
Collaborator

an example script

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces an example script to run PPO training for the qwen3_vl-235b-megatron model. The script configures a multi-node, multi-GPU training job with a large number of parameters for the verl.trainer.main_ppo script. My review identifies a critical issue in the parallelism configuration that would prevent the script from running successfully on the specified hardware. I've provided a suggestion to correct the parallelism settings.

Comment on lines +34 to +36
actor_rollout_ref.actor.megatron.tensor_model_parallel_size=4 \
actor_rollout_ref.actor.megatron.pipeline_model_parallel_size=8 \
actor_rollout_ref.actor.megatron.expert_model_parallel_size=8 \

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The current parallelism configuration for the actor model is invalid for the specified hardware. With trainer.n_gpus_per_node=8 and trainer.nnodes=8 (lines 79-80), the total number of GPUs is 64.

The Megatron-LM parallelism requires the data parallel size (DP) to be divisible by the expert parallel size (EP). The data parallel size is calculated as DP = total_gpus / (TP * PP).

With the current settings:

  • tensor_model_parallel_size (TP) = 4
  • pipeline_model_parallel_size (PP) = 8
  • expert_model_parallel_size (EP) = 8

The data parallel size would be DP = 64 / (4 * 8) = 2.

The constraint DP % EP == 0 becomes 2 % 8 == 0, which is false. This will cause the training to fail.

To fix this, you could adjust the parallelism settings. For a large MoE model on 64 GPUs, a configuration that increases data parallelism to accommodate more expert parallelism might be more suitable. For example:

actor_rollout_ref.actor.megatron.tensor_model_parallel_size=2 \
actor_rollout_ref.actor.megatron.pipeline_model_parallel_size=4 \
actor_rollout_ref.actor.megatron.expert_model_parallel_size=8 \

This configuration results in DP = 64 / (2 * 4) = 8, which satisfies the 8 % 8 == 0 constraint.

Suggested change
actor_rollout_ref.actor.megatron.tensor_model_parallel_size=4 \
actor_rollout_ref.actor.megatron.pipeline_model_parallel_size=8 \
actor_rollout_ref.actor.megatron.expert_model_parallel_size=8 \
actor_rollout_ref.actor.megatron.tensor_model_parallel_size=2 \
actor_rollout_ref.actor.megatron.pipeline_model_parallel_size=4 \
actor_rollout_ref.actor.megatron.expert_model_parallel_size=8 \

@ISEEKYAN ISEEKYAN mentioned this pull request Oct 17, 2025
5 tasks done
@ISEEKYAN
ISEEKYAN enabled auto-merge (squash) October 17, 2025 06:51
@ISEEKYAN
ISEEKYAN merged commit dd8864f into verl-project:main Oct 17, 2025
4 checks passed
masoudhashemi pushed a commit to masoudhashemi/verl that referenced this pull request Oct 19, 2025
wangboxiong320 pushed a commit to wangboxiong320/verl that referenced this pull request Nov 1, 2025
NenoL2001 pushed a commit to NenoL2001/verl that referenced this pull request Nov 3, 2025
chenjiaoAngel added a commit to chenjiaoAngel/verl that referenced this pull request Nov 14, 2025
chenhaiq pushed a commit to The-Hierophant/verl-1 that referenced this pull request Nov 18, 2025
NenoL2001 pushed a commit to NenoL2001/verl that referenced this pull request Nov 26, 2025
TimurTaepov pushed a commit to giorgossideris/verl that referenced this pull request Dec 20, 2025
vyomakesh0728 added a commit to vyomakesh0728/verl that referenced this pull request Jan 22, 2026
zwluestc pushed a commit to zwluestc/verl that referenced this pull request May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants