mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[GH-ISSUE #676] [question]: what are the differences between using the Transfer Engine in Mooncake and using UCX for communication? #214
Labels
No labels
ascend
auto-closed
bug
bug
CI/Build
Common
documentation
enhancement
feature request
good first issue
help wanted
high priority
MetaX
nightly-failure
pull-request
PyTorch Backend
question
RFC
Roadmap
stale
Store
Tests
Transfer Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kvcache-ai/Mooncake#214
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @njw1123 on GitHub (Jul 26, 2025).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/676
As a programmer who is not very familiar with communication, I would like to ask: what are the differences between using the Transfer Engine in Mooncake and using UCX for communication? They both seem to perform topology awareness and zero-copy (if supported by the hardware).
@njw1123 commented on GitHub (Jul 26, 2025):
Also, in the nixl repository, UCX can be replaced by the Transfer Engine, as they provide similar functionality.
@alogfans commented on GitHub (Jul 29, 2025):
Mooncake Transfer Engine is optimized for AI workloads, and our internal experiment shows that it outperforms UCX for small-sized I/Os.
@njw1123 commented on GitHub (Jul 29, 2025):
thanks for your reply.