deepseek-ai / deepseek-ai/3FS

Seeking Clarification on Data Transfer, KVCache Reading, and Optimization Routes

Open
#136 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
10.2k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

I apologize for raising an issue here to seek clarification, as despite conducting extensive research, I'm still confused. From my understanding, in the context of data transfer from the client to the server in 3FS, the path is
```client_DRAM -> RDMA -> server_DRAM -> directIO -> write to SSD.```
Is this correct?

Regarding reading the KVCache via 3FS, is the transfer route as follows:
```server_SSD -> directIO -> server_DRAM -> RDMA -> client_DRAM -> memcpy to GPU memory```?

Also, considering the availability of technologies like GPU Direct RDMA or GPU direct storage (such as with the A100), is it possible to optimize the route to
```server_SSD -> RDMA -> GPU_memory```?

Or could you please tell me where I can obtain further materials and plans regarding these topics.

Thank you in advance for your time. I look forward to your insights.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.