You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Renames all occurrences of thread_count (and write_thread_count at the
user-facing API level) to files_per_rank / write_files_per_rank for
transparency. The parameter controls how many files each rank writes to,
not a concurrency thread count, which is a separate concept in the
codebase.
Closes#66
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
1. Ensure you have sufficient space on your base container mount.
8
8
1. If you have enough memory, but are running out of buffer space during writes, you can:
9
9
1. Increase the default initial buffer size via `initial_write_buffer_size_bytes` in the `wrap` API you are using (the default is 16 GB).
10
-
1. Increase the write thread count, so that each rank writes to multiple buffers, effectively cutting the size of each buffer proportionally, via `write_thread_count` in the `wrap` API you are using (the default is 1).
10
+
1. Increase the number of files per rank, so that each rank writes to multiple buffers, effectively cutting the size of each buffer proportionally, via `write_files_per_rank` in the `wrap` API you are using (the default is 1).
11
11
12
12
### How can I clean up ML Flashpoint checkpoints after job completion?
0 commit comments