[GH-ISSUE #312] Does the concurrent writing of a single file support configuration #191

Closed
opened 2026-10-26 09:46:51 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @hhwode on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/312

When mounted inside the pod and executing torch.save to save checkpoints, the model size is divided into 5GB each. It appears to be a serial write with only 1 concurrency, which cannot improve speed. Does 3fs not support concurrent writing of individual files.
Testing the zero2 mode 7B model, a total of 120GB took nearly 10 minutes to write.

Originally created by @hhwode on GitHub (Jul 14, 2025). Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/312 When mounted inside the pod and executing torch.save to save checkpoints, the model size is divided into 5GB each. It appears to be a serial write with only 1 concurrency, which cannot improve speed. Does 3fs not support concurrent writing of individual files. Testing the zero2 mode 7B model, a total of 120GB took nearly 10 minutes to write.
Author
Owner

@SF-Zhou commented on GitHub (Jul 14, 2025):

​​3FS inherently supports concurrent write operations on a single file, but FUSE locks single-file write operations, preventing concurrency. Using usrbio is a feasible solution.​​

<!-- gh-comment-id:3067509659 --> @SF-Zhou commented on GitHub (Jul 14, 2025): ​​3FS inherently supports concurrent write operations on a single file, but FUSE locks single-file write operations, preventing concurrency. Using usrbio is a feasible solution.​​
Author
Owner

@hhwode commented on GitHub (Jul 14, 2025):

​​3FS inherently supports concurrent write operations on a single file, but FUSE locks single-file write operations, preventing concurrency. Using usrbio is a feasible solution.​​

Thanks, i will try it.

<!-- gh-comment-id:3068365347 --> @hhwode commented on GitHub (Jul 14, 2025): > ​​3FS inherently supports concurrent write operations on a single file, but FUSE locks single-file write operations, preventing concurrency. Using usrbio is a feasible solution.​​ Thanks, i will try it.
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/3FS#191
No description provided.