Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Question] Why use datatype ncclInt8 in nccl_all_to_all_scatter_async. #220

Open
cicirori opened this issue Dec 18, 2023 · 1 comment
Open

[Question] Why use datatype ncclInt8 in nccl_all_to_all_scatter_async. #220

cicirori opened this issue Dec 18, 2023 · 1 comment

Comments

@cicirori
Copy link

cicirori commented Dec 18, 2023 •
edited
Loading

Wondering why the ncclint8 datatype is used in the C++ implementation of nccl_all_to_all_scatter_async, whether it's for speed reasons or simply because don't want to support multiple datatypes through templates.

Thanks!
@ghostplant
Copy link
Contributor

According to bandwidth profiling, there is no speed difference between ncclInt8 x N and ncclInt32 x N / 4, so you can choose either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ghostplant @cicirori