Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Zero_Stage=1 results in higher TFLOPS?

Open
#48 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale

Research direction

Start with the 48-node contenders table in chronicles-prequel.md, linked from the issue, and compare the Zero Stage 0 and 1 rows and their recorded settings. Determine why the reported TFLOPS differ despite matching parameters, then clarify the explanation or correct the documentation so the result is understandable.

Written by the indexing model from the issue text.

Description

Description

I am learning the chronicles_prequel, and I find the last table in the chapter indicates the higher TFLOPS is achieved with Zero_Stage = 1.
Trying with ZeRO_STAGE=0/1
Zero_stage=1 could reduce the memory cost, but how come it increases the performance with other parameter being the same?

Nodes Size ZS DP TP PP MBS GBS Mem Sec/it TFLOPs Notes
48 181B 1 4 8 12 2 2048 37GB 120.29 134.02 02-21
48 181B 0 4 8 12 2 2048 72GB 137.34 113.02 02-21
Dominant language
Shell
Stars
1k
Forks
102
PR merge metrics
No merged PRs in 30d

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.

More from bigscience-workshop/bigscience

All issues in bigscience-workshop/bigscience

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.