[GH-ISSUE #569] low_latency dispatch_comm_bytes may differ when using BF16 precision. #349

Open
opened 2026-10-26 09:58:57 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @wehyy on GitHub (Jan 20, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/569

As shown below, i think we should recompute dispatch_comm_bytes when using bf16.

github.com/deepseek-ai/DeepEP@29d31c0957/tests/test_low_latency.py (L221)

Originally created by @wehyy on GitHub (Jan 20, 2026). Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/569 As shown below, i think we should recompute dispatch_comm_bytes when using bf16. https://github.com/deepseek-ai/DeepEP/blob/29d31c095796f3c8ece47ee9cdcc167051bbeed9/tests/test_low_latency.py#L221
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepEP#349
No description provided.